yashsingh1/xdaforums huggingface dataset:
[General Topics] mrmazak:
These tablets are booted to fastboot with a different command.

"adb reboot fastboot"

NOT "adb reboot bootloader"

If you get the recovery.img and boot.img uploaded I can try to patch them with the same process that I did last time.

I will not be able to test boot them since my tablet is different,

And if they work for you I can code them into my original tool from first post, and make the batch determine which files are needed for the connected device
[General Topics] lgally80:
So, Ive gotten close, but trying to do this the long, safe, and correct way is taking long. Having trouble disassembling and debugging the OS and sh!t and repackaging it. Would help if I wasnt nauseous from cancer treatment and homeless fml...
[General Topics] ezdi:
:silly: SMH. That's what I get for not finishing a project before leaving. I can get back in now. Not sure why the stock recovery or button methods don't work, though.

You got PM.

Is the bootloader signed? Or does unlocking the bootloader allow that to be arbitrarily replaced as well? I'm hoping a hex editor can turn a 30 into 1.
[General Topics] mrmazak:
That would be good to get rid of that wait time, but remember if your bootloader gets broken that's pretty much end of the like I think. Unless someone has a successful jtag have or something.
[General Topics] mrmazak:
try these

"fastboot boot **.img" only boot to test

In theory just booting test images is relitively safe, but things could go wrong and in the end as with all android modifications, what you do to your device is of your choice knowing the possible risk of loss of said device.
[General Topics] iHDD:
I get up to "5. Drivers for Intel Device". After the "adb reboot fastboot", go on my PC on the Device Manager, see my tablet flashing on and off, update device, go on the "Intel Android Device". both the "Android Bootloader Interface" and "Intel Android Bootloader Interface" ends up with "Windows encountered a problem installing the drivers for your device. Windows found drivers for your device but encountered an error while attempting to install them."

I have an Rca Voyager RCT6873W42-ANDROID6.0-V19-V1.16.50-E04
[General Topics] mrmazak:
Not 100% sure but maybe because you need to set windows to allow unsigned drivers. But I thought the Intel drivers were signed.

I know setting the driver was a little tricky.
[General Topics] ezdi:
w03 test results

Recovery seems to work. It can't mount /data without reformatting it first, but that's to be expected... I think? I tried the Magisk installer (planning to uninstall before rebooting) but it couldn't find the boot image. My guess is there's some fstab stuff missing or the installer can't deal with the funky by-name partition names. I haven't used CWM in a long time, so I don't know how to debug this. I'll worry about it later since I don't want to mess with the kernel until I can get back into fastboot.

Boot image works, but goes to the decryption error message and forces me to do a factory reset. With no way to get into the bootloader without a full boot, re-enabling adb, etc, I haven't been able to get it working yet because a normal boot takes a long time (I think it's re-encrypting and rebuilding dalvik cache, so I need to start again.).

Tomorrow I'll try booting CWM, reformatting /data, and then booting the boot image.

Are there any logs I can get you?

Do you have any links that helped you figure out how to modify the recovery/kernel? Is it as simple as catting an initrd to the stock kernel for recovery and changing boot args on the boot image? Binwalk isn't identifying either of the images I pulled as kernels.
[General Topics] mrmazak:
What I did was take your images and unpacked them using "Carliv Image Kitchen for Android v1.3" and copied you kernel-img and second-img into the cwm recovery and boot images from my rooted version.

I have no guide . you can read the thread where we rooted and made the modified boot and recovery

https://xdaforums.com/general/help/rca-voyager-rct6873w42-rooting-help-t3485625

I don't know if you can do the format data from cwm like you suggest. I know I did it from fastboot (fastboot format userdata)

So tablet booted and screen was working s that was the problem with v31 before when people "flashed" the rooted boot.img made for v19 it no longer had working screen. (Kernel problem)

It would then be same directions from the OP substituting those new boot.img and cwm-recovery.img instead. I did not make the modified stock recovery (I had that for adb use in stock recovery to be able to call "reboot fastboot")
[General Topics] ezdi:
I made the mistake of selecting "reboot bootloader" from the CWM advanced menu thinking it was doing the right thing under the covers so now it's several hours before trying again. Maybe I'll dig into the image and see if I can change it to fastboot.

Are you saying that I could flash the cwm-recovery? Or should I wait for/make modified stock recovery?
[General Topics] iHDD:
[MENTION=5312578]mrmazak[/MENTION]: I've allowed unsigned drivers to no avail, same problem. Do you think it may be because I have windows 10 32-bit? Worth a shot on my other laptop I suppose. Thanks nonetheless!
[General Topics] mrmazak:
I'm using win 10 64bit. But I do recall someone who was having driver issue swears it was win 10 giving him trouble. He used an older one and worked for him so, yeah give it a shot.
[General Topics] mrmazak:
No you can't flash cmw to tablet, it will not work on the inside.

But since the boot.img did boot and screen was on you

should

be able to flash that.

Imade the kernel change to the stock recovery now too, This is supposed to make it so adb will work from stock recovery. since there is no button combo that gets device into fastboot mode this is perhaps next best option.

Now for reasons that I do not understand the CWM recovery only works when booted and the stock recovery only works when flashed, This means if you boot this "stock_ish" recovery it will not work properly, It (at least on my tablet) puts recovery into a loop, but the display is shown. But when flashed it works. ¯\_(ツ)_/¯

now as long as the system adb has already been enabled and authorized then adb should work from recovery, mostly only for the purposes of rebooting to fastboot if needed. And there is also a default adb_key installed on the ramdisk of recovery that can be forced to load if needed in other cases, (but will require you to also put the adb private key that matches the one loaded inside the recovery on your pc)
[General Topics] iHDD:
rca-boot_permissive-20170316-1706.img for build V19 has no mirrors ?

But hey man, I really appreciate for all your time making/finding/etc for us, really helpful!
[General Topics] mrmazak:
I dont know when file-host will be fixed, but I uploaded boot.img again and here is alternate download link.

https://www.androidfilehost.com/?fid=961840155545581470
[General Topics] iHDD:
On my second laptop, works much better with This, though I've a new problem... I first tried with Intel Android Bootloader, it was still switching on and off and there was nothing after to work. So I then tried Android Bootloader, it stopped switching on and off (dunno if that's a good thing or bad thing?).

Well, sadly I don't recall in detail, but I did try the first time on A2's "Fastboot Devices" then shown much information, so I tried A3's "Fastboot flashing unlock" and failed.

I turned it off then set a normal restart. I did a "adb reboot Fastboot," turned blank with a fade black screen, but now there is no switching on and off and in the Devices Manager, there's no Portable Device (your Other Device). Despite that, still able to use adb commands, but just 1 line with the "Fastboot Devices" command

Have tried it a couple times with the same fate.

Did I ruin it? I don't really know, but it still works fine, just the Fastboot seems to no longer switch on and off.
[General Topics] mrmazak:
the end result seems about right, "Fastboot mode."

Now the failing to unlock.

did you set enable oem unlock toggle switch inside android developer options menu?

did you use volume up button or down?

try holding volume button before enter command in terminal.
[General Topics] rpk3:
Greetz-

Mrmazak- long time! I see your work has progressed. Nice Job.

BTW- you have any users with issues on the 6.0-v15.

Does your current tool release allow for this version?
[General Topics] ezdi:
Nope, no go. This recovery doesn't have a display and ADB is unauthorized. I tried booting normally, deleting the ADB authorization, and reauthorizing to see if that worked. I tried rebooting to recovery from ADB hoping that the authorization would stick around.

Do you have the private key somewhere? Then I could get in and see what is going on.

I haven't flashed the boot image yet. I'm trying to do minimal changes and recovery uses its own kernel anyway, right?
[General Topics] mrmazak:
I will take another look at the "stock" recovery. I actually used the recovery from V19 with your kernel, so I will do again with only the adbd and key this time.

For me, at least, using the built in key requires putting tablet into "adb sideload mode" . For some reason this makes it load or read the adb key i put into the recovery.

Otherwise it should be using the adb key generated by the system. And I am assumeing that the /data area is not being allowed to load, making recovery not to have screen

I will have new version to try tonight.
[General Topics] mrmazak:
I have not seen any files for V15. so it is not been worked on , and not allowed in the tool
[General Topics] mrmazak:
Try this version of the stock recovery. img file is inside zip
[General Topics] lgally80:
UGH!

I've tried everything everyone else has, and even a few variances, nothing. I'm very close to just physically modifying mine, which is not only ridiculous given the product's value and hardware, but also wildly tempting as the total loss in dollars is almost nil imo should it fail... I'd rather do that than get into my first idea, which is image the device, decompile/modify, repack, flash. I feel like this would be outrageously difficult as I'm quite sure everything is signed, encrypted, etc... Just had an idea while typing this, I wonder if I can direct the device to load Android OS from SD Card, and just let the stupid thing keep its internal memory untouched and thus bypassing the devices security in its entirety.... Lots to think about.... But I am very bored, and very determined lol. But here's my summary thus far of my 43 model: not guna happen, but I am well known for miracles :P
[General Topics] mrmazak:
What part have you been able to get to?

Did you get to boot the CWM and get a working root shell?

If so have you been able to dd copy the images of boot and recovery>
[General Topics] lgally80:
It's a long story, other half has the tablet right now but i'll post pics of what I found so far, might be valuable to someone else... To summize:

Imaged entire device manually, which did no good because encrypted, but was handy when I bricked the 3 times I did.

Never could get recovery flashed without issues, worked once but led to one of my bricks when it touched the other partitions during a root attempt.

Havent been able to find a viable update.zip option.

PC method flashing of OS partition failed and bricked bc security.

WTH RCA! This thing is junk, why are you protecting it so hard! Half tempted to contact manufacturer (NOT RCA, who just rebranded and packaged it), and see what they would be willing to divulge... I wonder how much one would cost straight from the source w/ code :P
[General Topics] mrmazak:
well if you get the cwm recovery to install inside tablet please let me know. Because we can only do a fastboot boot of that recovery. Because it fails when flashed to recovery partition.

I would also be quite appreachative if you would let us know how you "imaged the whole device". As far as I know , nobody here has been able to do that.

Oh wait a minute. Is your model 43 an intel or mtk processor?

I know they are voyager III but not the specs
[General Topics] mrmazak:
Has there been any tester for this recovery?
[General Topics] ezdi:
Sorry, working with another phone messed up my fastboot drivers in such a way that it seemed like the tablet was bootlooping.

This new recovery has a display, but no adb other than if I pick the sideload option. The sideload mode doesn't let me do anything (other than presumably sideload something), and I can't figure out how to back out without rebooting.

The kernel log contains a bunch of init: property_set("ro.blablabla" "blah") failed. The other log is empty.
[General Topics] mrmazak:
It might be related to /data still encrypted. And not being able to read the adb key. Or your adb is not authorized in system.

FYI.

test out this therory by turning tablet OFF> then try adb devices whith tablet off
[General Topics] iHDD:
Got up to "B: V19 2-a: type 'fastboot boot rca-boot_permissive-20170316-1706-2.img'", after I type "fastboot boot rca-boot_permissive-20170316-1706-2.img," it says "cannot load 'rca-boot_permissive-20170316-1706-2.img' : no such file or directory". I figure it's a simple whoops on my part?
[General Topics] mrmazak:
the command will change depending on where you have the file downloaded to.

so if it is in a folder (rca) in your default download location ic could be ,

"fastboot boot C:\Users\iHDD\Downloads\rca\rca-boot_permissive-20170316-1706-2.img"

or if the img file that you have downloaded is on your desktop it could be

"fastboot boot C:\Users\iHDD\Desktop\rca-boot_permissive-20170316-1706-2.img"

I usually have windows explorer window open next to the command window and just drag the file (img in this case) into the terminal , if you do the you would type

"fastboot boot "

then drag the file from explorer window to the tremnal window. Important, notice the"space" after "boot"
[General Topics] iHDD:
"D3: once loaded recommend to make backup," there's many options to upload, which one would you prefer?
[General Topics] mrmazak:
only 2 backup options. One to internal storage, one to extenal storage. Depends on if you have external sd-card or not.
[General Topics] iHDD:
Thanks for the clarification. But now, "adb remount" command says "remount failed: success," so did it fail or success? Lol... Sorry for many questions.
[General Topics] mrmazak:
That's okay. As long as it said success.
[General Topics] iHDD:
What do I do after D6, just turn my tablet off then back on or choose yes or no from "reboot system"?
[General Topics] iHDD:
Sorry, double post
[General Topics] mrmazak:
when recovery asks if you want to "fix" or "root" select no. then reboot
[General Topics] iHDD:
Awesome, works now! I really appreciate both your team(?) and your support, wouldn't have been able to work without you, thanks a ton! ?
[General Topics] Christopher12301:
ok

ok. but how do you uninstall the sd card without being able to put in commands on the fastboot screen. i seem to have soft bricked my tablet is why im asking and im having allot of trouble getting it unbricked
[General Topics] mrmazak:
He was refering to the external micro sd card, the one from the sd card slot. Not the internal memory

Little info on your "soft brick" maybe we can help.

FYI

this tablet allows for adb while powered off, so if you had enabled and autherized your pc, it might help you.
[General Topics] jmacie:
I had a brick back a couple months and did finally get another and got it rooted. Thanks for putting up the methods. I really appreciated it. I wonder was there ever any progress on getting the boot screen beyond that ~30 second delay before loading? I know it's been mentioned and I can't really complain, it's just not as handy to boot up quickly., and I know you have a definative answer. Thanks again, you're a star in my book!
[General Topics] mrmazak:
No . I have not made any progress on changing the ~30 delay
[General Topics] jmacie:
Thank you
[General Topics] chris5204:
Almost worked

I got to the last step in the instructions (using cwm to install superSu) and now my tablet seems to be stuck in a loop on the Voyager screen. I tried to get to the cwm screen but every time I try my tablet turns off. I hold down volume down and power button but the bootloader warning with the 30 second countdown has an option to turn off the tablet with the volume down button. It turns off every time. Any ideas?
[General Topics] niebaum:
Trying to boot recovery? It's actually volume up. From an off state, hold power and volume up until you see the bootloader unlock screen appear and then flash back off (immediately, not after the 30 seconds). As soon as it flashes off, release the buttons and it should attempt to boot recovery.
[General Topics] mrmazak:
I just try to confirm.

You said got to last step. So you did flash the modified boot.img.

Because during my testing I got the looping voyager screen when I did not flash the boot.img

Also the cwm recovery will not boot with button combo. It does not run when flashed to tablet. So I hope you did not flash the cwm to the device. That might make you stuck.

Hope you got the "modified" stock recovery installed and can get the button combo done to boot to it. Then adb should work and can "reboot fastboot"

If you did not install modified recovery you might be stuck also.

If you had booted the tablet during the process and re-enabled adb and autherized pc again, you might be able to get adb to connect while tablet is off.
[General Topics] chris5204:
I followed the v31 instructions and everything worked well until I tried to install the supersu.zip. Adb doesn't seem to work now. I hear the chime when I connect the tablet to my pc but when I try the reboot fastboot command it says error device (null) not found. I guess I have a brick now.
[General Topics] mrmazak:
are you able to turn it off?
[General Topics] chris5204:
Yes, I can turn it off.
[Android Q&A, Help & Troubleshooting] Designassist:
I own a Blu Life One 2015 X011Q. I am looking for either stock rom or custom. I've been searching everywhere and I end up in a forum for another similar named device. I am aware there is a whole line and some running media tek while others run qualcomm. I am running a qualcomm. I have twrp installed but can't get the phone to boot pass the Blu logo.
[Android Q&A, Help & Troubleshooting] mirfatif:
I have QMobile Z8 which is said to be same as Blu Life One (2015). I'm not sure about that. But if it's​ so, I can help you flash Q Mobile Z8 Stock Firmware.

Also Wiko Ridge 4G is same as QMobile Z8.
[Android Q&A, Help & Troubleshooting] Designassist:
Hi yes thank you for responding I did dig around and it is similar to the Blu running 4.4.4 kit Kat which I am. I would be very grateful if you could provide a link to the stock or if you know an already upload verison of the Qmobile z8
[Android Q&A, Help & Troubleshooting] mirfatif:
There are some flashable custom ROM's created by [MENTION=6793286]ASAZING[/MENTION] for Wiko Ridge 4G which is also same as QMobile Z8 and Blu Life One (2015). But I haven't been able to test these ROM's so far because no Custom Recovery works for me as I have explained in this post. Btw, which custom recovery you are using for your device?

Coming to the second option: Stock ROM, there isn't any flashable zip available. But Factory Firmware files are available online which can be flashed using QFIL detailed in this thread.
[Android Q&A, Help & Troubleshooting] Designassist:
I have twrp as my custom recovery I flashed and rooted with this link https://xdaforums.com/android/general/blu-life-one-xl-2015-build-ktu84p-root-t3229893

Now that I have twrp I just need a rom. I tried flashing the stock but was having problems I thought maybe it was the rom itself but did a little research and realized others were having problems too. It was solved by using mtk flash tools but since I have a qualcomm verison I did not know what to do I'm glad you direct me to a qual flasher that just might solve my problem. I'll keep you up to date.
[Android Q&A, Help & Troubleshooting] ASAZING:
Team Panther

Hello..

If you get the source code of the Blu Life One 2015

Can i help them compile Cyanogenmod 12.1 :D
[Android Q&A, Help & Troubleshooting] Designassist:
Well I tested the QZ mobile and wiko ridge theory and flashed this custom rom@ https://xdaforums.com/android/development/rom-miui-v6-wiko-ridge-fab-4g-qmobile-t3165157 it worked except for my screen kept autorotating upside down with all google apps. I had this same problem with another phone I ported with a rom similar to it. I had to change some files in the recovery image itself but it was for upside down on everything. This time its only limited to gapps related apps. Any clues or should i start googling?
[Android Q&A, Help & Troubleshooting] ASAZING:
COOL

Changed the kernel and dt.img? :confused:
[Android Q&A, Help & Troubleshooting] Designassist:
I tried flashing two other boot. Img but it just hangs on the logo. I did it through fastboot flash boot boot. Img. I'm at a lose I had to put the phone in rotation lock. Do you know any compatible kernels? Now that I had time to explore the rom I realized all the apps that have rotation capabilities are upside down I even went into the build. prop and add the line ro. sf. hwrotation=180. :eek:
[Android Q&A, Help & Troubleshooting] ASAZING:
Bro

Uses prebuilt kernel and dt.img to adapt a twrp
[Android Q&A, Help & Troubleshooting] mirfatif:
Try this Stock ROM
[Android Apps and Games] GravitApp:
Hi,

What do you think guys about this one game:

https://play.google.com/store/apps/details?id=com.ak.zombie.pub

https://www.youtube.com/watch?v=HxRhT9ZzJ0c

:good: ? Let me know! And kill da zombie!! :p
[Nexus 6 Q&A, Help & Troubleshooting] pcrussell50:
I have my original Nexus 6 charger that supports the Qualcomm Quick Charge 2.0. But I don't have the usb cable any more... or don't know where it is. I heard that you have to have a quick charge compatible cable. I have a TON of cables, and I'd like to try them out on my quick charger, but I'd like to know if quick charge is working at a quick glance. Is there a way?

-Peter
[Nexus 6 Q&A, Help & Troubleshooting] Isley_:
Download Ampere app from Playstore, once you open it, it'll start measuring your charge rate. It'll also tell you if it's turbo charge, you can also tell it's fast charge if you get like 1800-2000+ mAh.
[Nexus 6 Q&A, Help & Troubleshooting] cameraddict:
I'm using the cable from my old '12 N7 with my N6 charger... charges to full in about 90 minutes or so (from 10% to 30+% in about 15-20 minutes). I'd say feel your device after about 5-10 minutes of charging... if it's as hot as hot tap water, you're probably quick charging. When I charge with other chargers, it gets warm , but not hot.
[Nexus 6 Q&A, Help & Troubleshooting] pcrussell50:
thanks guys. i downloaded Ampere late last night. in a nod to both of you, when quick charging, Ampere was showing about 2200mA and when regular charging, it was showing about 650mA. and when quick charging, it was noticeably hotter.

i thought that you were supposed to use special quick charge cables, but i tried a handful of different cables this morning on my N6 quick charger and they all would charge at or above 2000mA. if anyone knows any specific info about cables, i would love to read about it, but otherwise i'm pretty happy that i'm quick charging again.

-Peter
[Nexus 6 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
The only specific info regarding cables is to avoid "charge only" types, which are frequently found with Logitech products. Charge only cables have the two center pins disabled, which neuters the quick charge system. In quick charging, power is sent through the data lines (the two center pins) as well as the power lines, which results in a faster charge.

There is no way of telling you have a charge only cable just by looking at it. It has to be plugged in.
[Nexus 6 Q&A, Help & Troubleshooting] Larzzzz82:
Some cables, like the one in this pic have the awg or mm sq size on them.https://goo.gl/photos/5ni5wofvnaBUpot6A

I'm willing to bet the larger wire (24 awg) is carrying the charging current.
[Nexus 6 Q&A, Help & Troubleshooting] pcrussell50:
More great info, guys thanks a bunch