Root has been achieved for rca tablet, With the intel atom chip
Basic steps are Just like many android devices.
1. Unlock boot loader
2. Flash modified stock recovery
3. Test boot a permissive boot.img
4. Flash permissive boot.img (if test boot was ok)
5. Boot into Custom recovery and flash superSu.
The modified recovery has adb active. This is needed to get back into bootloader mode if flashing goes wrong.
Because on the RCA tablet there is no button combination for bootloader boot mode.
Steps that the included tool performs:
First step tool does is ask soc type. (intel or MTK) for this guide it needs to be intel.
1. Guides user through the bootloader unlock steps.
adb reboot fastboot
verifies the status of unlocked or not
verifies the ability to do unlock in not already unlocked
fastboot flashing unlock
fastboot format userdata
fastboot format cache
fastboot reboot
2. Fastboot boot generic CWM recovery. To use its root shell for copying devices boot.img and recovery.img
3. Use Carliv Android Image kitchen tools to unpack the pulled boot.img and recovery.img
RECOVERY
4. copy adbkey.pub from pc running the patch to stock-recovery\ramdisk\data\misc\adb\adb_keys
copy adbkey.pub from pc running the patch to stock-recovery\ramdisk\adb_keys
this s done to ensure an authorized adb connection to device even after factory reset and data format
5. Edit recovery\ramdisk\default.prop as follows:
"ro.secure=1" to "ro.secure=0"
"ro.debuggable=0" to "ro.debuggable=1"
"persist.sys.usb.config=mtp" "persist.sys.usb.config=mtp,adb"
add line: persist.service.adb.enable=1
add line: persist.service.debuggable=1
6. Use Carliv Android Image kitchen tools to re-pack recovery
BOOT
7. copy adbkey.pub from pc running the patch to stock-boot\ramdisk\data\misc\adb\adb_keys
copy adbkey.pub from pc running the patch to stock-boot\ramdisk\adb_keys
this s done to ensure an authorized adb connection to device even after factory reset and data format
8. Edit boot\ramdisk\default.prop as follows:
"ro.secure=1" to "ro.secure=0"
"ro.debuggable=0" to "ro.debuggable=1"
"persist.sys.usb.config=mtp" "persist.sys.usb.config=mtp,adb"
add line: persist.service.adb.enable=1
add line: persist.service.debuggable=1
9. Edit boot\ramdisk\*fstab* as follows:
"forceencrypt" to "encryptable"
10. Add these lines to boot/ramdisk/init.rc after the line that starts: "on init"
# root use Permissive
write /sys/fs/selinux/enforce 0
11. Swap sepolicy and /sbin/adbd with permissive (insecure) versions included in tool "/img" folder
12. Use Carliv Android Image kitchen tools to re-pack boot
CWM
13. Use Carliv Android Image kitchen tools to unpack the generic CWM
14. copy stock-recovery\recovery.img-kernel to unpacked generic CWM folder (replacing file that is there)
copy stock-recovery\recovery.img-second to unpacked generic CWM folder (replacing file that is there)
15. Use Carliv Android Image kitchen tools to re-pack CWM
SECOND / FLASH MENU
16. fastboot boot patched boot.img
used to verify patched image does not cause device to brick
17. fastboot flash boot patched-boot.img
flashes patched-boot (user must have verified boot image works in previous step)
then formats /data to remove encryption
18. fastboot flash recovery patched-recovery
stock recovery does not seem to work when booted, so test booting pached image not done
this modified recovery is needed to be able to get back to bootloader mode if trouble occurs.
19. Load patched CWM
loads patched recovery to be used to flash SuperSu and also to make device "back-ups"
Updated 2-4-2018 Multi-platform-patch-tool
==>>Multi-platform-patch-tool
Downloads Needed:
Download adb=fastboot 15 second instal == https://forum.xda-developers.com/showthread.php?t=2588979
Download intel drivers == https://software.intel.com/en-us/protected-download/385047/494732
Download SuperSu.zip == https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Thanks:
@vampirefo for most of the needed parts to make this work. CWM, permissive su-policy, without that this would not be possible
@bluefirebird For the image unpack tool
Youtube video I found , of someone explaining how he used the files to root his device.
Video is from before patch tool written. Video was from when individual build files were available.
New method of patching individual device files , removes possibility of flashing files from wrong device.
History of this root method started in this thread.
https://forum.xda-developers.com/general/help/rca-voyager-rct6873w42-rooting-help-t3485625
Tablet hangs on bootloader unlock screen due to the volume keys not responding. Also, on first connect with fastboot flashing unlock, tablet responds with power key every time unless unplugged from usb. Upon second attempt, the power button key issue stops, but the volume keys do not function on the bootloader unlock screen.
Grishak said:
Tablet hangs on bootloader unlock screen due to the volume keys not responding. Also, on first connect with fastboot flashing unlock, tablet responds with power key every time unless unplugged from usb. Upon second attempt, the power button key issue stops, but the volume keys do not function on the bootloader unlock screen.
Click to expand...
Click to collapse
Are you using this with correct drivers?
And with working voyager tablet, with an Intel soc. This does not work with an m version tablet(mtk soc)
I never had problems with volume key not recognized
It's the RCT6873W42 with the Intel Atom. I'll check the drivers, but it reads the power button, just not the volume buttons.
---------- Post added at 04:45 PM ---------- Previous post was at 04:28 PM ----------
I have verified driver installation. Fastboot will not recognize volume up or down. Power button is the only one registering a key event. (4) EV_POWER received.
Grishak said:
It's the RCT6873W42 with the Intel Atom. I'll check the drivers, but it reads the power button, just not the volume buttons.
---------- Post added at 04:45 PM ---------- Previous post was at 04:28 PM ----------
I have verified driver installation. Fastboot will not recognize volume up or down. Power button is the only one registering a key event. (4) EV_POWER received.
Click to expand...
Click to collapse
What about the allow OEM unlock toggle in the developer options screen?
I do not know how to verify key presses as you refer to.
So cannot compare on my end.
There may be different versions released with same model number.
I will make note in the op with the model and build number of my tablet, and can also include a link to the thread where the boot.img was built and tested.
But your problem seems to be before you can even get to that point.
OEM Unlock is enabled. This is my fourth android root, I have yet to ever run into an issue with the volume keys not registering during fastboot. The confirmation screen to unlock the bootloader is visible, but I am unable to select yes or no. The only button that functions is the power key, it times out after 70 seconds. Perhaps if there were a way to extend that timeout period, the volume keys could function. I have attempted removing the usb cable after initiating the flash unlock command, also plugging it into an alternative charger, removed and entered headphones to trigger the volume control. I turned up a search on an individual that had an issue with RCA not programming the volume keys into the Bootloader Unlock screen. Different model, but that was the only thing I managed to find. Strange.
Grishak said:
OEM Unlock is enabled. This is my fourth android root, I have yet to ever run into an issue with the volume keys not registering during fastboot. The confirmation screen to unlock the bootloader is visible, but I am unable to select yes or no. The only button that functions is the power key, it times out after 70 seconds. Perhaps if there were a way to extend that timeout period, the volume keys could function. I have attempted removing the usb cable after initiating the flash unlock command, also plugging it into an alternative charger, removed and entered headphones to trigger the volume control. I turned up a search on an individual that had an issue with RCA not programming the volume keys into the Bootloader Unlock screen. Different model, but that was the only thing I managed to find. Strange.
Click to expand...
Click to collapse
I did see that same issue with an earlier release on an rca tablet.
My build number is :
RCT6873W42-ANDROID6.0-V19-V1.16.50-E04
Kernel:
3.14.0+
Patch level:
June 1, 2016
Also the directions I had when unlocking was to hold volume up button before giving the "fastboot flashing unlock" command to avoid a timing problem.
I did not have the problem either way.
https://forum.xda-developers.com/android/general/firmware-rca-viking-pro-rct6303w87dk-t3325158
That RCA Viking Pro tablet, that was the reference to the volume keys not being programmed.
---------- Post added at 10:34 PM ---------- Previous post was at 10:01 PM ----------
Android Version: 6.0.1
Kernel Version: 3.14.0 Aug 22 19:31:40 CST 2016
Build number: RCT6873w42-ANDROID6.0-V31-V1.17.70-W01
Patch Level: June 1, 2016
I had a dream that it was an SD card holding me back. Sure enough, there was an SD card installed in the tablet which was preventing me from unlocking the bootloader. So as of now, it is unlocked and I will proceed with your directions and post an update shortly.
After flashing the modified boot file on step B, my tablet screen is black with the backlight. I can not interact with the tablet except for volume down disconnecting the device and turning the backlight off. Also
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set;
So basically if the authorization for ADB is gone AND my screen is gone...
I have the RCA Voyager RCT6973W43 will this work on it
Wphall said:
I have the RCA Voyager RCT6973W43 will this work on it
Click to expand...
Click to collapse
Well I have the same model, my screen is now useless after unlocking the bootloader and flashing the first image. Am now searching for a new tablet. The issue immediately began right after rebooting from the successful flashing. Black screen, android set up the os and configured itself, screen still inactive. Debug is disabled now and I have no way to access the tablet via ADB/fastboot now. Out of ideas.
Update
After attempting to blindly access recovery *nothing will display on screen* and I have learned that my volume down button shuts off the screen and disconnects the tablet from my pc for a moment. Also I am positive the touch screen is no longer active, windows picks up the tablet as a storage device. I am thinking that it is the end of for this tablet.
Grishak said:
Well I have the same model, my screen is now useless after unlocking the bootloader and flashing the first image. Am now searching for a new tablet. The issue immediately began right after rebooting from the successful flashing. Black screen, android set up the os and configured itself, screen still inactive. Debug is disabled now and I have no way to access the tablet via ADB/fastboot now. Out of ideas.
Update
After attempting to blindly access recovery *nothing will display on screen* and I have learned that my volume down button shuts off the screen and disconnects the tablet from my pc for a moment. Also I am positive the touch screen is no longer active, windows picks up the tablet as a storage device. I am thinking that it is the end of for this tablet.
Click to expand...
Click to collapse
;;
That is unfortunate. I would have expected you to stop when knew the build numbers and kernel versions were different.
recovery has nothing to do with the boot.img, so your stock recovery should still be there. From powered off hold volume button closer to the usb cable, and the power button for about 10 seconds. the wait for the warning screen to count down. (30 seconds)
should be at recovery.
Do you have the bootloader untrusted screen after unlocking.?
What do you mean "android set up the os and configured itself" ?
did you do the userdata format? that is needed to decrypt the tablet. as the /data area from factory is force-encrypted.
Basically after unlocking the bootloader and flashing the first image... my tablet screen has been rendered useless. It is completely unusable and all of this happened before you posted the version number.
---------- Post added at 12:28 PM ---------- Previous post was at 12:26 PM ----------
I followed all instructions described up to the end of Step B. Upon completion of step B, my tablet screen has been rendered useless. Either it conveniently died at the worst time, or something during the flashing caused it. Either way, I have removed the battery, checked connections and can't find anything. Backlight, black screen. 24/7 can't get anything else to display. Can't do a thing with it.
---------- Post added at 12:32 PM ---------- Previous post was at 12:28 PM ----------
Well, I hope this brick helps others not make the same mistake, LOL!
I picked up the tablet for $20 months ago and have been waiting for a root.
Now it's dead so I guess it's time for a better tablet until this one is on sale again!
Wphall said:
I have the RCA Voyager RCT6973W43 will this work on it
Click to expand...
Click to collapse
No, this root is device specific.
Sent from my Life_Max using Tapatalk
---------- Post added at 08:50 AM ---------- Previous post was at 08:49 AM ----------
Grishak said:
Basically after unlocking the bootloader and flashing the first image... my tablet screen has been rendered useless. It is completely unusable and all of this happened before you posted the version number.
---------- Post added at 12:28 PM ---------- Previous post was at 12:26 PM ----------
I followed all instructions described up to the end of Step B. Upon completion of step B, my tablet screen has been rendered useless. Either it conveniently died at the worst time, or something during the flashing caused it. Either way, I have removed the battery, checked connections and can't find anything. Backlight, black screen. 24/7 can't get anything else to display. Can't do a thing with it.
---------- Post added at 12:32 PM ---------- Previous post was at 12:28 PM ----------
Well, I hope this brick helps others not make the same mistake, LOL!
I picked up the tablet for $20 months ago and have been waiting for a root.
Now it's dead so I guess it's time for a better tablet until this one is on sale again!
Click to expand...
Click to collapse
Bricking your tablet would be the expected outcome, as this root was never ever meant for your tablet.
Sent from my Life_Max using Tapatalk
Looks like I'll have a nice battery and screen for a raspberry pi.
vampirefo said:
No, this root is device specific.
Sent from my Life_Max using Tapatalk
---------- Post added at 08:50 AM ---------- Previous post was at 08:49 AM ----------
Bricking your tablet would be the expected outcome, as this root was never ever meant for your tablet.
Sent from my Life_Max using Tapatalk
Click to expand...
Click to collapse
I was rooting my tablet from "out of the box" according to the directions, and everything was fine up until the same point. After flashing the modified boot img, formatting userdata and cache, and issuing the fastboot reboot command, now all I get is a backlit screen. Volume down does turn the screen black for a moment then lights back up. The pc sees it as a flash drive, but adb devices doesn't see it at all (not even as an unauthorized device).
My tablet is the correct model. RCT6873W42
I haven't figured out how to get into the recovery. Holding volume up + power, etc doesn't do anything.
---------- Post added at 09:33 AM ---------- Previous post was at 09:17 AM ----------
Grishak said:
Looks like I'll have a nice battery and screen for a raspberry pi.
Click to expand...
Click to collapse
I'm having the identical problem on the identical step you did, and I have the correct model/version.
icaruspony said:
I was rooting my tablet from "out of the box" according to the directions, and everything was fine up until the same point. After flashing the modified boot img, formatting userdata and cache, and issuing the fastboot reboot command, now all I get is a backlit screen. Volume down does turn the screen black for a moment then lights back up. The pc sees it as a flash drive, but adb devices doesn't see it at all (not even as an unauthorized device).
My tablet is the correct model. RCT6873W42
I haven't figured out how to get into the recovery. Holding volume up + power, etc doesn't do anything.
---------- Post added at 09:33 AM ---------- Previous post was at 09:17 AM ----------
I'm having the identical problem on the identical step you did, and I have the correct model/version.
Click to expand...
Click to collapse
All I can think to do at this point is to add an md5 to verify the files downloaded are the ones intended to be used.
It would seem before people try to root their device they should first know and be able to get into recovery before they attempt to root.
If you can't get into recovery via hardware keys, there is no point to continue trying to root your device until you figure that part out.
I don't have the exact tablet in this thread, Mine is close enough though.
to get into my recovery.
press and hold volume down and power until splash screen pops up, I get a splash screen just before count down screen, release and when 30 second count down finishes tablet boots into recovery.
vampirefo said:
It would seem before people try to root their device they should first know and be able to get into recovery before they attempt to root.
If you can't get into recovery via hardware keys, there is no point to continue trying to root your device until you figure that part out.
I don't have the exact tablet in this thread, Mine is close enough though.
to get into my recovery.
press and hold volume down and power until splash screen pops up, I get a splash screen just before count down screen, release and when 30 second count down finishes tablet boots into recovery.
Click to expand...
Click to collapse
I have 49 more of these tablets, still in their boxes, to test with.
Related
Hello
I bought an haipai i9377 (mtk6577). short after that i rooted it, (succesfull then when i tried to flash clockwork mod recovery( wich was build with CWM builder) it said ok but it ain't ok! (unsuccesfull
Now it wont boot and now i am stuck, i can still come into recovery. but download mode is not working any more.
Adb keeps telling me the device ' 1234567890abcdefg" dont know why that name, is offline BUT recognises it. when i put it in recovery windows detects it as an unknown device and when i install drivers it wont start. i don' t have really much options now i do got an backup of my recovery, bootloader and system image. But without getting into download mode or CWM i cant do really much with it ? HELP
P.S When there is no accu in it and put it into cable windows detects it for 2 seconds (preloader usb vcom android) ; Sound something is in* sound something is putted out*
Just had exactly the same problem here, Tried to update the bootloader and now I get nothing but the spinning nexus android logo and the USB is no longer being detected. Did you fix it?
---------- Post added at 08:36 AM ---------- Previous post was at 08:24 AM ----------
OK well 5 mins later I managed to fix it, Went into 'Factory' Mode - Hold down power, Menu Key and Volume down for about 4 seconds - As the tex came up on the screen to start the auto test, hold volume up to cancel the auto test, Menu appears - Select Clear eMMC - and it will reboot - all fixed.
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Keithn said:
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Click to expand...
Click to collapse
Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.
Keithn said:
Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.
Click to expand...
Click to collapse
Could you send me stock recovery so I can take a look inside the init.rc
Yeah, I'll do that today
Sent from my One M8
Keithn said:
Yeah, I'll do that today
Sent from my One M8
Click to expand...
Click to collapse
I found it inside the stock nvidia images for testing on the k1 board thanks.
This appeared to be the issue https://github.com/cm-ardbeg/androi...b4fd46180/rootdir/etc/init.recovery.ardbeg.rc
Unjustified Dev said:
I found it inside the stock nvidia images for testing on the k1 board thanks.
This appeared to be the issue https://github.com/cm-ardbeg/androi...b4fd46180/rootdir/etc/init.recovery.ardbeg.rc
Click to expand...
Click to collapse
If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.
Keithn said:
If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.
Click to expand...
Click to collapse
I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working
Unjustified Dev said:
I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working
Click to expand...
Click to collapse
Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB configuration descriptor failed.
for device status.
I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________
Nothing in Ubuntu either, even lsusb doesn't list it.
Keithn said:
Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB configuration descriptor failed.
for device status.
I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________
Nothing in Ubuntu either, even lsusb doesn't list it.
Click to expand...
Click to collapse
This is crazy does adb work in the recovery you compile from their git?
Unjustified Dev said:
This is crazy does adb work in the recovery you compile from their git?
Click to expand...
Click to collapse
I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.
Keithn said:
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Click to expand...
Click to collapse
I am having same issue
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
Keithn said:
I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.
Click to expand...
Click to collapse
I have same issue but have a boot loop so I am bricked at the moment
---------- Post added at 02:55 AM ---------- Previous post was at 02:50 AM ----------
Okay now when I also enter recovery mode I have a blank screen can not boot into the system because of a boot loop, does anyone have any surgestions ?????????
MRobbo80 said:
I am having same issue
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
I have same issue but have a boot loop so I am bricked at the moment
---------- Post added at 02:55 AM ---------- Previous post was at 02:50 AM ----------
Okay now when I also enter recovery mode I have a blank screen can not boot into the system because of a boot loop, does anyone have any surgestions ?????????
Click to expand...
Click to collapse
go into fastboot and flash a recovery then boot into recovery
Just tested stock recovery and the device doesn't even show as being connected until I select sideload then all I get is sideload.
Keithn said:
go into fastboot and flash a recovery then boot into recovery
Just tested stock recovery and the device doesn't even show as being connected until I select sideload then all I get is sideload.
Click to expand...
Click to collapse
My screen is black I can not see any options I am using the custom new cwm
Did you try what I said? Can you at least get into the boot loader?
Sent from my SHIELD Tablet
Keithn said:
Did you try what I said? Can you at least get into the boot loader?
Sent from my SHIELD Tablet
Click to expand...
Click to collapse
sorry not sure how to boot in to fastboot?
MRobbo80 said:
sorry not sure how to boot in to fastboot?
Click to expand...
Click to collapse
I meant to say boot into the bootloader so you can use fastboot. From Nvidia
Code:
HW method:
Turn off the device
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
So basically just hold vol - then press power and keep the vol button held but not the power. Should give you a black screen with some words on it and you can select a few different things. When you are there use fastboot like you would adb. Get a cwm image and give it the command
Code:
fastboot flash recovery cwm.img
Put what ever name and location you have for your recovery image in place of cwm.img.
Keithn said:
I meant to say boot into the bootloader so you can use fastboot. From Nvidia
Code:
HW method:
Turn off the device
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
So basically just hold vol - then press power and keep the vol button held but not the power. Should give you a black screen with some words on it and you can select a few different things. When you are there use fastboot like you would adb. Get a cwm image and give it the command
Code:
fastboot flash recovery cwm.img
Put what ever name and location you have for your recovery image in place of cwm.img.
Click to expand...
Click to collapse
Thanks for your fast reply here is whats happening I have been working with a dev to get acip up and running, I have cwm recovery and have fully wiped the device and installed acip which currently is bootlooping. Now my problem is when I try to enter fastboot holding down -volume key and pressing the power it just splashes to the boot logo so no luck there but when I hold down volume + and power key I can hear the sound of a usb connecting to my computer but have a black screen only. So when I check device manager under windows I can see a yellow caution mark APX unknown device so at the moment trying to find a driver that will work so that's where I am really
MRobbo80 said:
Thanks for your fast reply here is whats happening I have been working with a dev to get acip up and running, I have cwm recovery and have fully wiped the device and installed acip which currently is bootlooping. Now my problem is when I try to enter fastboot holding down -volume key and pressing the power it just splashes to the boot logo so no luck there but when I hold down volume + and power key I can hear the sound of a usb connecting to my computer but have a black screen only. So when I check device manager under windows I can see a yellow caution mark APX unknown device so at the moment trying to find a driver that will work so that's where I am really
Click to expand...
Click to collapse
Grab theses and see if they work. They are included with Nvidias tegra development tools.
Nvidia Drivers (shouldn't be much different than googles drivers but here they are.)
I don't think you are going to want it in APX anyways. I noticed it can be a pain to get the bootloader try keeping vol - held and only pressing power for a couple of seconds at most and give it a second for the screen to turn on. If you hit the splash screen then you missed the bootloader.
Keithn said:
Grab theses and see if they work. They are included with Nvidias tegra development tools.
Nvidia Drivers (shouldn't be much different than googles drivers but here they are.)
I don't think you are going to want it in APX anyways. I noticed it can be a pain to get the bootloader try keeping vol - held and only pressing power for a couple of seconds at most and give it a second for the screen to turn on. If you hit the splash screen then you missed the bootloader.
Click to expand...
Click to collapse
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:07 AM ----------
MRobbo80 said:
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
Click to expand...
Click to collapse
My tablet is now fully restoring my backup in cwm as I speak have one big grin on my face at the mo.
MRobbo80 said:
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:07 AM ----------
My tablet is now fully restoring my backup in cwm as I speak have one big grin on my face at the mo.
Click to expand...
Click to collapse
No problem good to hear :good:
My device now boots to the android logo, says "orange state, this device has been unlocked and cant be trusted" and then shows battery charging screen and will not boot.
How can I boot it into recovery/bootloader so I can relock the bootloader?
I see that the MTK Preloader is avalable at boot via USB so is there a way to use that to boot it into fastboot or relock the bootloader?
JakesDen said:
My device now boots to the android logo, says "orange state, this device has been unlocked and cant be trusted" and then shows battery charging screen and will not boot.
How can I boot it into recovery/bootloader so I can relock the bootloader?
I see that the MTK Preloader is avalable at boot via USB so is there a way to use that to boot it into fastboot or relock the bootloader?
Click to expand...
Click to collapse
Did this happen when you were trying to root your phone?
Anyway to enter bootloader, connect your phone to your laptop, hold down the power button and the volume up button. After some seconds you should see a countdown. You can release the buttons when the countdown reaches 0
Does exactly the same thing, device wont turn on by holding power button when it is not connected to usb either. Are you ture this is a TA-1020?
I think the buttons may have disconnected inside.......
JakesDen said:
I think the buttons may have disconnected inside.......
Click to expand...
Click to collapse
Ouch!
If you're not worried about your warranty, you can try opening it up. On the other hand, why not take it to HMD/Nokia support?
Because they know me and they wont do **** :3
Any chance of you chatting with me over Discord / IRC for easier messaging?
JakesDen said:
Any chance of you chatting with me over Discord / IRC for easier messaging?
Click to expand...
Click to collapse
Sorry, I don't use either of them
I did accidently disconnect the buttons when I took it apart earlier to disconnect the battery as it doesn't "boot in 5 seconds" like it says and holding down the power button does nothing and wont make it reboot.
The button combination does nothing. I will have to use SP Flash Tools to create a backup and see if I can manualy relock bootloader....
It seems to work now, locked bootloader and it seems to boot, currently stuck on "powered by android" logo, might be taking a while after supersu first boot? I'll check logs if it doesn't boot in the next 30 mins.
JakesDen said:
I did accidently disconnect the buttons when I took it apart earlier to disconnect the battery as it doesn't "boot in 5 seconds" like it says and holding down the power button does nothing and wont make it reboot.
Click to expand...
Click to collapse
So basically your phone isn't starting up at all. Do you think you can put the buttons back together? Also one other thing, whenever my phone doesn't start up, 5 seconds holding the power button is usually not enough. I generally have to hold the power button and the volume up button and hold for 20 - it doesn't actually reach 20 but usually exceeds 10 seconds
---------- Post added at 05:32 PM ---------- Previous post was at 05:30 PM ----------
JakesDen said:
It seems to work now, locked bootloader and it seems to boot, currently stuck on "powered by android" logo, might be taking a while after supersu first boot? I'll check logs if it doesn't boot in the next 30 mins.
Click to expand...
Click to collapse
It seems you replied while I was typing my last response.
Anyway 30 mins is long enough. I think it should start up before then
It seems to work as in show the android screen and work for file access over MTP but it doesn't look like it is gonna pass the android logo.
reflash phone using OST
Can anyone here provide stock partitions for the TA-1020?
the_laser said:
reflash phone using OST
Click to expand...
Click to collapse
I use linux... I guess i'll just use virtualbox and usb passthrough then.
Where can I get stock rom for TA-1020 and working OST from?
I tried flashing NE1-215H-0-00WW-B02.nb0 from https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487
However it boots and is stuck in the "powered by android" screen, don't think it's the correct rom for the TA-1020, can anyone find one for my device?
redweaver said:
So basically your phone isn't starting up at all. Do you think you can put the buttons back together? Also one other thing, whenever my phone doesn't start up, 5 seconds holding the power button is usually not enough. I generally have to hold the power button and the volume up button and hold for 20 - it doesn't actually reach 20 but usually exceeds 10 seconds
---------- Post added at 05:32 PM ---------- Previous post was at 05:30 PM ----------
It seems you replied while I was typing my last response.
Anyway 30 mins is long enough. I think it should start up before then
Click to expand...
Click to collapse
Do you know what's wrong?
JakesDen said:
I tried flashing NE1-215H-0-00WW-B02.nb0 from https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487
However it boots and is stuck in the "powered by android" screen, don't think it's the correct rom for the TA-1020, can anyone find one for my device?
Click to expand...
Click to collapse
NE1-147I-ind-0-00WW-B02.nb0 and NE1-147C-UAE-0-00WW-B01.nb0 are also for the nokia3. I don't know if anyone of them will work with the TA-1020 though
Confirmed works. Also make sure to flash magisk!
I went through setup, enabled unlock bootloader, unlocked the bootloader, used `fastboot boot TWRP.img` in order to boot into twrp, I then flashed magisk and rebooted back to android.
After that I rebooted into bootloader and used `fastboot flash recovery TWRP.img`.
If you don't flash magisk and keep the bootloader unlocked then you wont get passed the "orange state".
If you don't flash magisk but flash recovery then you wont be able to get passed the "red state".
That is why I booted into TWRP and installed magisk before I actualy flashed anything.
I will create a guide later.
i use magisk module and ,y phone cant boot normally. bootloop on t-mobile screen. how i can enter twrp?
You enter Twrp the same way you enter the stock recovery. With phone off press and hold the power and volume down button. As soon as the first screen pops up (i believe its the lg logo) continue holding volume down but quickly release power button and then repress and hold it down again. Then follow the prompts click yes to wipe phone, instead of wiping the phone it'll put you into TWRP.
---------- Post added at 10:13 AM ---------- Previous post was at 10:09 AM ----------
Some Magisk modules are only for certain phones or OS. I had the same problem after installing a module that was supposed to help the gpu. The dev didnt say it was for a specific phone or OS, but i assume that it was. Always make sure to read the notes of the module.
So I think my phone is ****ed, I've tried everything I can think of so hopefully some of you more knowledgeable folks can chime in.
My main phone is a Galaxy S20 5G, but I bought a pixel 3a off of Swappa because I still love pure Android and for the Camera (this was before I had the S20 and had an S10). I had the disposable income so why not?
I've been using it a lot lately because I carry both sometimes. My method for security on my 3a is finger prints, but I had pattern also. I decided to make it a password instead of pattern since it's more secure, and I think I fat fingered the password because it wouldn't take it.
I went to find my device on Google and locked it, gave it a temporary password, but it's not taking it and I'm 99.9% certain it's the one I created, literally 40 seconds apart lol...
I tried to unlock it in ADB but it's locked in Fastboot so it wouldn't let me Fastboot unlock, flash all (insert random rom), Fastboot erase, or -w because it says it can't because the device is locked (in Fastboot, this phone is locked in more than one way lol...).
I can't factory reset it and I don't know the temporary password and when I try the lock option on Google again it doesn't find the phone even though it's connected to my Wi-Fi and I even put my sim card in it and tried LTE.
Am I ****ed or is there something I can do that I haven't tried yet?
Please, if anyone has any ideas I will buy you a damn beer if you help me. Bump.
Edit: please read everything before you do it so that you know what is going it to happen.
In fastboot, try the command *fastboot flashing unlock* WARNING THIS WILL ERASE ALL FILES
Now download the sargo factory images from this website and unzip it.
Now run the flash-all.bat/.sh depending on what operating system you use, but for windows use the .bat
If it boots into the operating system, dont do anything but just shut it down and reboot into fastboot (Power+VolUp)
Now run *fastboot flashing lock* THIS WILL REMOVE ALL FILES AGAIN.
PS: You cant restore a backup since you are going to need the password for that.
---------- Post added at 09:11 AM ---------- Previous post was at 08:54 AM ----------
Second reply, since I believe I misread your question a bit.
You were saying that you cant fastboot flashing unlock, if that is the case, try this:
Turn off your your device, boot to recovery mode by pressing and holding power button and volup button. If you see no command, then hold the power button and quickly press the volume up button. Then you should be in recovery mode. Then keep pressing volume down until you are on Wipe data/factory reset, and press the power button.
Hope that worked.
Tiebe said:
Edit: please read everything before you do it so that you know what is going it to happen.
In fastboot, try the command *fastboot flashing unlock* WARNING THIS WILL ERASE ALL FILES
Now download the sargo factory images from this website and unzip it.
Now run the flash-all.bat/.sh depending on what operating system you use, but for windows use the .bat
If it boots into the operating system, dont do anything but just shut it down and reboot into fastboot (Power+VolUp)
Now run *fastboot flashing lock* THIS WILL REMOVE ALL FILES AGAIN.
PS: You cant restore a backup since you are going to need the password for that.
---------- Post added at 09:11 AM ---------- Previous post was at 08:54 AM ----------
Second reply, since I believe I misread your question a bit.
You were saying that you cant fastboot flashing unlock, if that is the case, try this:
Turn off your your device, boot to recovery mode by pressing and holding power button and volup button. If you see no command, then hold the power button and quickly press the volume up button. Then you should be in recovery mode. Then keep pressing volume down until you are on Wipe data/factory reset, and press the power button.
Hope that worked.
Click to expand...
Click to collapse
I love you, that second part worked! If you want a beer bought for you just let me know.
C-4Nati said:
I love you, that second part worked! If you want a beer bought for you just let me know.
Click to expand...
Click to collapse
I'm only 13
But thanks anyway!