Develop Bugs

[Q] attempted kitkat revert, almost completely unresponsive

I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?

flyingsherpa said:
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
Click to expand...
Click to collapse
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything

noahvt said:
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
Click to expand...
Click to collapse
I have to confess my ignorance here... I'm brand new to flashing android like this so I don't know the answer to your question. If part of tutorial I followed blanks out the bootloader (and doesn't write something in?)... then you're probably right. I shall look into this more tonight when I'm at home with the nexus. Thanks for at least giving me something to look into, that's exactly what I was hoping for!

This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Asus_USA said:
a7medmo7eb - We're very sorry to hear of this. Kindly email us at [email protected] with this copied problem description along with the serial number of your tablet and we will do our best to provide you with troubleshooting and servicing options.
If you have any further questions, comments or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you.
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
Click to expand...
Click to collapse

nhizzat said:
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Click to expand...
Click to collapse
Thanks, you're probably right. I did read up to understand all this stuff a bit more, so I know it's not lack of a bootloader or anything. All img files install just fine, so my pc can talk to the nexus, just the screen is all wonky no matter what i do.
Unfortunately I bought this 1.5 years ago so I don't think it's under warranty anymore. Everything was fine until I updated to Lollipop! Seems a big coincidence that I had a hardware failure at the same time as that update... I feel like Google ruined my tablet...

There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you

Masterchief87 said:
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Click to expand...
Click to collapse
Hmm, thanks for the idea, but fastboot wouldn't do "format data", giving me the error: Formatting is not supported for filesystem with type ' '
Googling that makes it not look good. Weird, thing is, it still technically boots up, just the screen is so wonky you can't see where you are or interact with it properly. Not sure what else to try (opening it up and re-seating touchscreen cables?).

How to find original build version when soft bricked?

Ok, I have searched the internet and these forums for hours and have not seen an answer to this anywhere.
I can't believe I'm the only person who has ever wanted to know how to determine this information!
I repair Nexus 7 2013 as a hobby - usually with broken screens, but now and then buy a soft bricked one.
I have the same issue every time - trying to find what is the original build number when it is soft bricked and you can't access Recovery either. I have even tried to see if Asus has a cross reference of serial number to original build number - no they don't.
I use the Wug tool and so far the score is 3 saved, one that even has Wug stumped, and the one I'm working on tonight that I simply can't get to work.
I always have to guess and try versions. tonight I've tried the single version of 4.4.4 and 3 other version of 5 to 6. Each time the best that I can get is a sluggish boot that usually eventually freezes while trying to run setup. That is BEST CASE. Worst case would take pages to describe. It sort of works on lmy47v a little and not at all on any other build. Manufacture date is March 2015.
If I didn't know better, if this was a PC, I would say there is a bad RAM chip.
Regardless, I would feel a lot happier if I knew I was installing the right build which leads back to the original question - how do you find the original build if it's soft bricked?
Thanks to anybody who can answer this!

Do this:
PC: download TWRP image, e.g. twrp-2.8.6.0-flo.img
N7: boot in fastboot mode
PC run: fastboot boot twrp-2.8.6.0-flo.img
N7: in TWRP UI mount system
PC run: adb shell cat /system/build.prop > build.prop.txt
View build.prop.txt on PC:
Code:
ro.build.id=LMY48Y
ro.build.display.id=cm_flo-userdebug 5.1.1 LMY48Y ceb9c142ee test-keys
ro.build.version.incremental=ceb9c142ee
But why do you bother to restore "original build number"?
Most of them are locked and will lose all data in the process of unlocking.
Then why not flash the latest OS image?

k23m said:
Do this:
PC: download TWRP image, e.g. twrp-2.8.6.0-flo.img
N7: boot in fastboot mode
PC run: fastboot boot twrp-2.8.6.0-flo.img
N7: in TWRP UI mount system
PC run: adb shell cat /system/build.prop > build.prop.txt
View build.prop.txt on PC:
Code:
ro.build.id=LMY48Y
ro.build.display.id=cm_flo-userdebug 5.1.1 LMY48Y ceb9c142ee test-keys
ro.build.version.incremental=ceb9c142ee
But why do you bother to restore "original build number"?
Most of them are locked and will lose all data in the process of unlocking.
Then why not flash the latest OS image?
Click to expand...
Click to collapse
Thanks for your reply. No less complicated way to find that out eh? I'm afraid that's a bit over my head (or perhaps its just the way its worded - no offense intended). If it was PC, and particularly DOS, I would be laughing.
When nothing else was working on this particular tablet, I did try for the heck of it to use the Wug toolkit to root and install TWRP, and it would just lock up and never install - no error messages or anything.
As far as why not use the most recent image, there are lots of opinions, and the majority I have ever read says if you don't use the original build you will get all kinds of problems right up to completely bricking the device. Since you have to take every opinion with a grain of salt, it just seems to make sense to use what it came with. 2 out of 3 tablets I have been able to do that with I have be able to save. Only 1 where I used a random build worked.

consumer61 said:
No less complicated way to find that out eh?
Click to expand...
Click to collapse
The simplest way is to check it in stock recovery but you say it is not an option...
consumer61 said:
the majority I have ever read says if you don't use the original build you will get all kinds of problems right up to completely bricking the device
Click to expand...
Click to collapse
Please post a link to one of them.

k23m said:
Please post a link to one of them.
Click to expand...
Click to collapse
I wish I could. Just random things read from hundreds of pages over a couple of years, and of course when you look for them you can't find them. I have on and off been trying to find an answer to this question for over a year.
Even the wug toolkit encourages you to make a backup of your own system rather than re-flash a random stock image. Since as soon as you unlock you lose everything anyway, there hardly seems any purpose to a backup as opposed to just re-flashing with the newest version - ergo that also leads you to believe you need to use the exact version that was there before.
I don't discount the possibility that even though not said, what was actually meant was that each device model has a version specific to it. Again, that was never clearly said, I am just using logic based on your concept that you can install any image at all, with absolutely no issue.

consumer61 said:
I wish I could... when you look for them you can't find them.
...rather than re-flash a random stock image.
Click to expand...
Click to collapse
That's it, all those horror stories are from "random stock" flashers. If you choose wisely the very latest stock image then there is no danger whatsoever.
Let's talk about the latest case - is it unlocked already?

I was able to unlock, but could not access recovery - when booting to recovery it would still just sit at the Google logo.
In order, I tried from the list that comes up on the Wug tool, a 6.01 version, then lmy47v, then lmy48g, then finally thought I would try going back quite far since there was only one version for 4.4.4 - ktu84p, then finally lmy48t.
With tiny variations, all had the exact same result - no errors when wiping or reloading. The circling balls would just around as normal, then eventually grind to halt - moving a tiny bit every 5-30 seconds. After maybe an hour, sometimes you would finally get the normal "pick your language" screen, although most times, after about 30 min I would just shut it down and power it back on.
That would result in sometimes getting the "pick a language". Sometimes able to get as far as entering a gmail address, but the system would always lag - registering a touch many seconds after doing it. Once single time, I got a full boot up. Then it came up with the OTA as it should. ran it, and back to soft bricked.
Also a couple of the times I was able to get it to boot, as soon as you would reboot, it would be back to soft bricked.
Motherboard got exceptionally hot, and battery was down to 18% once, and 27% another time from full charge - so it was working abnormally hard
I have been playing with and building pc' etc since the Vic 20, C 64 and so on, and it behaves just like a bad RAM chip. I did find a post on here saying the Kingston/Toshiba chip can get corrupted and must be replaced, with a link to the same guy selling MB on ebay - can't remember his id on here, but here is the ebay sale:
http://www.ebay.ca/itm/121637666631?_trksid=p2055119.m1438.l2649&ssPageName=STRK:MEBIDX:IT
Overall this is similar behaviour although not quite as bad, as the other motherboard that stumped Wug. He finally said it must be hardware in that case, and I certainly tend to think the same thing here.

consumer61 said:
He finally said it must be hardware in that case, and I certainly tend to think the same thing here.
Click to expand...
Click to collapse
Let's find out exactly. As you are comfortable with DOS then the following should be piece of cake:
download twrp-2.8.6.0-flo.img from https://dl.twrp.me/flo/
go to Wug(NRT)\data folder - can you see fastboot.exe and adb.exe there?
boot the Nexus in fastboot mode (when off press power+vol.down), connect it to your PC
in Wug's data folder open a DOS command window and copy/paste: fastboot boot twrp-2.8.6.0-flo.img [Enter]
when TWRP is up and running, copy/paste in the DOS: adb shell dmesg > dmesg.txt [Enter]
you will find dmesg.txt in Wug's data folder
zip up the file and attach it to your next post
This is THE hardware log and another chance to play with DOS-like stuff :laugh:

Ok excellent instructions. (did tech support for years).
I had pulled the MB and replaced it, so I just switched it back.
Install TWRP worked fine. TWRP screen came up.
Typed command for the msg file, and dos error was "error: device '<null>' not found
I know of TWRP, but have never used it. I hit the centre button on the screen which brought up what appears may be an install log, and its full of errors.
Goes down over a full screen, but the common statement is:
"unable to find partition size for /boot" /recovery /misc and about 15 more lines.
Also other errors like unable to mount cache, data, system
I just took a photo of the screen but it seems you can't post actual images, only links to images stored on the internet, not something off your hard drive.
Just to let you know, I did try various spacing around the dmesg > dmesg.txt command just to be sure, same error every time.
Now that is from the TWRP screen with all the buttons on it. If you meant for me to open a certain function of TWRP, I didn't.
Regards,
UPDATE: had a brainwave and loaded up Wugfresh and device manger. Showed exclamation mark beside the device so re-installed adb driver. Now the log worked. It is only 64k, and both the twrp photo and the log file should be attached now.

I looked through the log, and even not knowing the internals of the system that well, only one part stood out as appearing bad:
<3>[ 0.277130] msm_gpiomux_install: write failure: -22
<3>[ 0.277221] msm_gpiomux_install: write failure: -22
<3>[ 0.277404] msm_gpiomux_install: write failure: -22
<3>[ 0.277496] msm_gpiomux_install: write failure: -22
<3>[ 0.277648] msm_gpiomux_install: write failure: -22
<3>[ 0.277740] msm_gpiomux_install: write failure: -22
<6>[ 0.278656] Registering gpio keys
<6>[ 0.278778] Reconfigure VOL_UP(GPIO155) and VOL_DOWN(GPIO189) with PMIC
<4>[ 0.278991] 8921_l17: Failed to create debugfs directory
<4>[ 0.280609] ------------[ cut here ]------------
<4>[ 0.280700] WARNING: at arch/arm/mach-msm/subsystem_restart.c:573 subsys_restart_init+0xd8/0x104()
<4>[ 0.280883] Modules linked in:
<4>[ 0.281066] [<c0015f44>] (unwind_backtrace+0x0/0x11c) from [<c007ae88>] (warn_slowpath_common+0x4c/0x64)
<4>[ 0.281250] [<c007ae88>] (warn_slowpath_common+0x4c/0x64) from [<c007aeb8>] (warn_slowpath_null+0x18/0x1c)
<4>[ 0.281433] [<c007aeb8>] (warn_slowpath_null+0x18/0x1c) from [<c0c0c600>] (subsys_restart_init+0xd8/0x104)
<4>[ 0.281616] [<c0c0c600>] (subsys_restart_init+0xd8/0x104) from [<c0008718>] (do_one_initcall+0x8c/0x15c)
<4>[ 0.281799] [<c0008718>] (do_one_initcall+0x8c/0x15c) from [<c0c00a24>] (kernel_init+0xe8/0x1a4)
<4>[ 0.281982] [<c0c00a24>] (kernel_init+0xe8/0x1a4) from [<c000fdf8>] (kernel_thread_exit+0x0/0x8)
<4>[ 0.282104] ---[ end trace ff63e6c2cba9c001 ]---

consumer61 said:
Typed command for the msg file, and dos error was "error: device '<null>' not found
Click to expand...
Click to collapse
When TWRP is running please type adb devices and it should respond like:
Code:
List of devices attached
087777e8 recovery
If not, re-plug USB cable, check Windows device manager for new hardware. You may need ADB driver but Wug would install it before.
Please upload the picture(s) to http://imgur.com/?noFlash
We don't need to interact with TWRP for this task at all.
Btw, TWRP was not flashed, but only temporarily booted so you may need to repeat it all over again.
Cheers

I suspect you were writing your reply above, as I updated the info. Please see the end of page 1 - the photo and the log file are attached.
simply put is was my mess up - adb had to be re-installed every time you plug a device in when running XP Pro. (Yes I know XP. Hate 7 and 8 and 10, but this is the last version where you had SOME semblance of control over your own computer lol)
Thanks!

consumer61 said:
I suspect you were writing your reply above, as I updated the info. Please see the end of page 1 - the photo and the log file are attached.
simply put is was my mess up - adb had to be re-installed every time you plug a device in when running XP Pro. (Yes I know XP. Hate 7 and 8 and 10, but this is the last version where you had SOME semblance of control over your own computer lol)
Thanks!
Click to expand...
Click to collapse
Yes.
I use Linux and ...XP too :highfive:
Please check my last post here.

Help with Note 4 please

I may have a bricked phone on my hands, my fault I guess.
Although, I feel TWRP should share at least some of the blame.
I'm hoping someone can help to get me going again.
Last Xmas I got a refurbished Note 4 from Ebay and followed directions
here to root it. This all went well, I put TWRP 3.0.2 and Jasmine on it,
and it has worked just fine since then.
A couple days ago I realized I hadn't made a Nandroid backup of my phone
lately so I went into TWRP and did so. This went just fine and I stored
the backup on the external SD card.
A few hours later I bought a cheap home controller from Ebay. The controller
brand name is "Vera" and despite all of the negative comments on Google Play
I went ahead and installed the app. For the next day or two my phone began to
hang, stall, hesitate, whatever... and I remembered installing that app from
Google play so I went into the app manager and selected the uninstall option.
This caused the phone to hang indefinitely, I had to cycle the power button to
regain control. I then went back to Google Play and downloaded an uninstaller
program, told it to uninstall the vera app. It tried for a long time but
eventually gave up. "Uninstall failed" was all it would say.
So to stop this Vera app from hanging my phone I ran a freeze program ("Freeze"
is the actual name of the program) and had the vera app frozen. This worked, my
phone began to respond normally again. But I didn't like having this bad software
in my phone and that is when I remembered the recent TWRP backup.
I decided to do a complete restore with TWRP. TWRP did a restore of boot - (success),
recovery - (success), system - (success), data - "ERROR extractTarFork() process ended
with ERROR=255". Thanks TWRP, that really tells me a lot...
I repeated the restore effort a total of three times and same results. Google
wasn't much help, one suggestion was to unmount the data partition and try again.
Same results. Same error. Another suggestion was “stop and learn how to fix it”, well
sure, but I need a solution right now, I don’t have time right now for the learning part.
This is probably my first *big* mistake, I exited TWRP to see If I could boot
the OS and maybe fix it from there, (factory restore or something...). As you might
have guessed, it wouldn't boot the system with an incomplete data partition. I
suspected it too but I was desperate to try something. It would have been nice if TWRP
had warned me not to exit, instead of just saying "error 255..." because now it wont
boot back into recovery, just hangs. Odin mode appears to be working but I suspect it isn't.
It looks like it enters odin mode just fine, but odin can't see it.
So here is where it stands at the moment:
SYSTEM - Wont boot. Shows the Samsung logo, shows "custom", hangs at this point.
RECOVERY- Wont enter recovery mode. Small text in upper left says it is entering recovery
mode then it hangs.
ODIN/DOWNLOAD - Appears to enter this mode, usual screen appears, will not communicate
with Odin, will not communicate with adb.
One other note, the external sd card has a copy of the twrp log file written to it, as well
as the nandroid backup. But plugging the sd card into an adapter and then into a pc... It
says it can’t read it, and would I like to format it(?).
And of course there is valuable information on the phone.
I've run out of ideas, I'm asking anyone who is still reading this lengthy message(apologies)
for any other options, suggestions, any hope at all, instead of just throwing it in the trash.
Thanks for reading. I hope the dialog was understandable.
RT
UPDATE:
Progress. I have odin talking with the phone now, was able to re-flash TWRP and boot into it.
Still getting error 255. I am under the impression that this means I am out of space???
I pulled the recovery logs with adb, here is the relevant lines:
==> extracting: //data/app/radiotime.player-1/lib/arm/libtunein.uap.so (file size 5499572 bytes)
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
Iperation_end - status=1
I still don't understand "error 255" well enough to proceed. Google is not a wealth of information when it comes to this subject. Any suggestions on how to proceed are greatly appreciated.
thanks!
RT
LAST UPDATE:
I want to thank everyone here for all the help. Or the lack there of.
Since I had Odin and TWRP both working, I reconstructed the phone from scratch.
Re-rooted and re-installed Jasmine. So I am back up and running now, I just need
to get all the apps re-installed and configured.
But I must say that I am really disappointed with the lack of support from this forum.
It used to be that people were falling all over each other to help others out.
But 3 days and 49 views and not one of you had anything to say.
I guess that's what happens to all forums sooner or later, the newbies here don't know what
to say and are just looking for answers to their own issues, and the regulars become jaded
over time and can't be bothered anymore.
I used to think this forum was awesome, but now its just another forum like all the rest.
I will look to other websites for any future learning.
To the Admin: (If you can be bothered for a moment)You can close this thread, I consider
the issue resolved, and you can close my account too, I won't be back.
Good luck to you guys.
RT

RootieTootie said:
I may have a bricked phone on my hands, my fault I guess.
Although, I feel TWRP should share at least some of the blame.
I'm hoping someone can help to get me going again.
Last Xmas I got a refurbished Note 4 from Ebay and followed directions
here to root it. This all went well, I put TWRP 3.0.2 and Jasmine on it,
and it has worked just fine since then.
A couple days ago I realized I hadn't made a Nandroid backup of my phone
lately so I went into TWRP and did so. This went just fine and I stored
the backup on the external SD card.
A few hours later I bought a cheap home controller from Ebay. The controller
brand name is "Vera" and despite all of the negative comments on Google Play
I went ahead and installed the app. For the next day or two my phone began to
hang, stall, hesitate, whatever... and I remembered installing that app from
Google play so I went into the app manager and selected the uninstall option.
This caused the phone to hang indefinitely, I had to cycle the power button to
regain control. I then went back to Google Play and downloaded an uninstaller
program, told it to uninstall the vera app. It tried for a long time but
eventually gave up. "Uninstall failed" was all it would say.
So to stop this Vera app from hanging my phone I ran a freeze program ("Freeze"
is the actual name of the program) and had the vera app frozen. This worked, my
phone began to respond normally again. But I didn't like having this bad software
in my phone and that is when I remembered the recent TWRP backup.
I decided to do a complete restore with TWRP. TWRP did a restore of boot - (success),
recovery - (success), system - (success), data - "ERROR extractTarFork() process ended
with ERROR=255". Thanks TWRP, that really tells me a lot...
I repeated the restore effort a total of three times and same results. Google
wasn't much help, one suggestion was to unmount the data partition and try again.
Same results. Same error. Another suggestion was “stop and learn how to fix it”, well
sure, but I need a solution right now, I don’t have time right now for the learning part.
This is probably my first *big* mistake, I exited TWRP to see If I could boot
the OS and maybe fix it from there, (factory restore or something...). As you might
have guessed, it wouldn't boot the system with an incomplete data partition. I
suspected it too but I was desperate to try something. It would have been nice if TWRP
had warned me not to exit, instead of just saying "error 255..." because now it wont
boot back into recovery, just hangs. Odin mode appears to be working but I suspect it isn't.
It looks like it enters odin mode just fine, but odin can't see it.
So here is where it stands at the moment:
SYSTEM - Wont boot. Shows the Samsung logo, shows "custom", hangs at this point.
RECOVERY- Wont enter recovery mode. Small text in upper left says it is entering recovery
mode then it hangs.
ODIN/DOWNLOAD - Appears to enter this mode, usual screen appears, will not communicate
with Odin, will not communicate with adb.
One other note, the external sd card has a copy of the twrp log file written to it, as well
as the nandroid backup. But plugging the sd card into an adapter and then into a pc... It
says it can’t read it, and would I like to format it(?).
And of course there is valuable information on the phone.
I've run out of ideas, I'm asking anyone who is still reading this lengthy message(apologies)
for any other options, suggestions, any hope at all, instead of just throwing it in the trash.
Thanks for reading. I hope the dialog was understandable.
RT
UPDATE:
Progress. I have odin talking with the phone now, was able to re-flash TWRP and boot into it.
Still getting error 255. I am under the impression that this means I am out of space???
I pulled the recovery logs with adb, here is the relevant lines:
==> extracting: //data/app/radiotime.player-1/lib/arm/libtunein.uap.so (file size 5499572 bytes)
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
Iperation_end - status=1
I still don't understand "error 255" well enough to proceed. Google is not a wealth of information when it comes to this subject. Any suggestions on how to proceed are greatly appreciated.
thanks!
RT
LAST UPDATE:
I want to thank everyone here for all the help. Or the lack there of.
Since I had Odin and TWRP both working, I reconstructed the phone from scratch.
Re-rooted and re-installed Jasmine. So I am back up and running now, I just need
to get all the apps re-installed and configured.
But I must say that I am really disappointed with the lack of support from this forum.
It used to be that people were falling all over each other to help others out.
But 3 days and 49 views and not one of you had anything to say.
I guess that's what happens to all forums sooner or later, the newbies here don't know what
to say and are just looking for answers to their own issues, and the regulars become jaded
over time and can't be bothered anymore.
I used to think this forum was awesome, but now its just another forum like all the rest.
I will look to other websites for any future learning.
To the Admin: (If you can be bothered for a moment)You can close this thread, I consider
the issue resolved, and you can close my account too, I won't be back.
Good luck to you guys.
RT
Click to expand...
Click to collapse
sorry we missed your call gratz on the working phone . you know what they say "give a man a fish he ****s up his phone .....

Please help me to unbrick my Surface RT

I used bitlocker for my surface RT. I forget the password and the recovery key then I try to reset my device using recovery USB it failed at 2%
so I check my disk using diskpart. There is no partition on Disk 0. I can't do anything to the disk. it's just showing the capacity.
When I try to covert the disk to gpt (convert gpt) I got this error message
Virtual Disk Service error:
The object is not found.
Sorry for my bad English
Thank you.

surface tab RT
nesan95 said:
I used bitlocker for my surface RT. I forget the password and the recovery key then I try to reset my device using recovery USB it failed at 2%
so I check my disk using diskpart. There is no partition on Disk 0. I can't do anything to the disk. it's just showing the capacity.
When I try to covert the disk to gpt (convert gpt) I got this error message
Virtual Disk Service error:
The object is not found.
Sorry for my bad English
Thank you.
Click to expand...
Click to collapse
Did you ever find out how to un-brick your RT surface?

xm8 said:
Did you ever find out how to un-brick your RT surface?
Click to expand...
Click to collapse
No

Same issue - today I decided I wanted to do a full reset and followed what MS' site said to do (click "Skip this drive"). Looks like all that does is brick the device, great.
Mine's a Surface 2. I've done resets on this Surface 2 before, but I'd not click "Skip this drive" and instead put in the bitlocker key (which I would retrieve from the URL specified on that page).
I can barely even find any information about the diskpart error... but I guess all this means is that this Surface 2 (or at least its eMMC drive) is toast, which randomly had its touchscreen stop working a couple years ago (around the time of this post, huh). I'd like to believe it's due to some sort of security on the Surface 2 though... maybe.
Edit: Found one other thread out there on the internet of a user encountering the same issue when attempting to create partitions with diskpart on Surface 2: https://www.computing.net/answers/hardware/diskpart-cant-create-new-partition/94440.html Now I wonder if there's anyone who's _succeeded_ in doing diskpart operations on a Surface 2...

Diskpart works fine on these devices, Surface RT / 2 are quite hard to brick. Can you get to the command prompt using a USB recovery drive?
Do the following:
Diskpart
sel dis 0
clean
exit
This will fully clear the drive - then run recovery as normal.
https://support.microsoft.com/surfacerecoveryimage

jwa4 said:
Diskpart works fine on these devices, Surface RT / 2 are quite hard to brick. Can you get to the command prompt using a USB recovery drive?
Do the following:
Diskpart
sel dis 0
clean
exit
This will fully clear the drive - then run recovery as normal.
https://support.microsoft.com/surfacerecoveryimage
Click to expand...
Click to collapse
Yes, can run those commands (even did a clean /all), but restarting the recovery process fails at the same point (2%). Can't recall where but there's a script in the recovery zip that shows the diskpart commands it runs to clean, convert disk to GPT, create partitions etc. and fails for presumably the same reason.
I know it's attempting to run diskpart commands at this point: Since my touchscreen is broken (firmware probably, randomly stopped working and no amount of resets have fixed it) and its type cover is broken, I at first tried resetting by swapping a USB keyboard and the USB stick while going through the steps. It failed after a few seconds without any indication of progress. When I checked out the partitions with diskpart at this time, all 4 partitions were there and disk was marked as being GPT. When I finally decided to just use a type cover from another Surface (thus avoiding the USB swapping I was doing), this time I also received a "repartition drives?" prompt and selected yes. (Apparently, swapping out the recovery USB drive seems to dismiss the ask to repartition drives.) Recovery failed at 2%. Checked diskpart, and saw the drive with 0 partitions and not GPT - as if it did a `clean` with diskpart.
May be useful to note that ever since the touchscreen randomly stopped working back in at least 2018, my Surface 2 has had problems that appear to be symptoms of disk-related issues. I can't recall them all, but things like dism always reported issues with integrity, disk usage always pegged around 100%, and the last issue I tried to perform a reset for was the settings app just refusing to open (consistent app crash after splash screen). Other issues were that it would not wake from sleep (leading me to set it to never sleep). I can't recall if I ran any chkdsks or other stuff; I'll see if I can find any logs I may have exported. I had used the device quite often for years leading up to that, though of course ever since end of 2018 it's been just sitting around off or plugged in.

Need help unbricking Firestick 4K

I have 2 firestick 4ks.
Both identical in that they are rooted and debloated with (the same) various system apps frozen...
Both been running fine for a month or so...
Where I live I get frequent power cuts.
Yesterday after a power cut... one reboots correctly the other just goes to a black screen.
I connected it to my PC and ADB into it, I reenabled all apps via adb and rebooted, it just went to the same black screen.
So I booted to TWRP and reflashed RBoxes prerooted image, still nothing...
I then installed a stock image (Skel40's).... Still nothing.
Up to this point I had only been wiping Cache & Dalvik and dirty flashing.
I figured that there was a corrupted file that was affecting full boot, so I made the mistake of wiping data and installing stock again...
When I rebooted I had lost ADB!
I could still see the firestick in windows, however it just comes up as "Fire" in device manager with no ADB..
I grabbed an OTG cable and booted to TWRP and tried a few more times... each time gave exactly the same black screen (no orange amazon logo).
Finally I tried wiping system as well in case something was corrupted and reflashed stock.... Still nothing!
So I don't really know where to go from here... (I'm going to backup the other firestick and restore that over this one then reflash stock and see where that gets me...)
Does anyone have any ideas! I can get into TWRP, but I'm not sure it's wiping or flashing things correctly...
Any help greatly appreciated... Thx

Have you done any of the ideas listed in the other thread? Let me know if i can help #lockdown

Michajin said:
Have you done any of the ideas listed in the other thread? Let me know if i can help #lockdown
Click to expand...
Click to collapse
Hi Michajin...
Thanks for taking the time to help
I'll fill you in as to what I have and haven't tried...
I have wiped all standard partitions ( cache, dalvik, data, system) and reflashed both rooted and stock images *.*.6.8 and *.*.7.1
I think I may have wiped the Vendor partition, I'm not sure.
Under backup in TWRP I can see the Vendor partition, however under Wipe I see an extra 2 partitions (both) called storage and having not made a backup (I know!... )
I did'nt realise that the storage partition(s) may have been the Vendor partition.
After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal.
A couple of points that I can tell you...
I can boot to TWRP
I can reboot to hacked Bootloader
When I connect the firestick to my windows PC It's senses it straight away for a bout 10 seconds then drops it... It then senses it again and stays connected to my PC.
Windows recognizes it under portable devices as simply "fire" and an empty explorer window pops up, if I right click on the firestick in windows explorer (it shows as drive) I can pull a properties page which shows its serial number...!
On both my firesticks I have modified my build.prop for a faster boot which doesn't show the splash screen.
Both sticks were modified identically about a month ago and once setup had nothing added to them. They just get used for Kodi and catch-up TV apps.
I root them so as to boot directly into Kodi and freeze the bloat.
Both sticks have been rebooted multiple times.. This one failed after a powercut...
I been reading in the main rooting thread and have come across something about sticks not booting properly due to dm_verity failing and having to flash magisk before (or after... I'm not sure) the image flash.
I'm still reading through the thread so haven't tried anything yet... When i get head round what it is, I'll try.
The other 2 ideas I thought to try was to
1) flash an image directly from the bootloader (if possible.. I need to find more info on this) and
2) taking a backup of the working stick and trying that (It's in use a lot... due to #TotalLockdown! we're at 4 weeks with heavy police curfew! So I haven't had access to it)
If have any ideas or thoughts... I would be very grateful. Also I'm happy to try anything...

tinybilbo said:
Hi Michajin...
Thanks for taking the time to help
I'll fill you in as to what I have and haven't tried...
I have wiped all standard partitions ( cache, dalvik, data, system) and reflashed both rooted and stock images *.*.6.8 and *.*.7.1
I think I may have wiped the Vendor partition, I'm not sure.
Under backup in TWRP I can see the Vendor partition, however under Wipe I see an extra 2 partitions (both) called storage and having not made a backup (I know!... )
I did'nt realise that the storage partition(s) may have been the Vendor partition.
After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal.
A couple of points that I can tell you...
I can boot to TWRP
I can reboot to hacked Bootloader
When I connect the firestick to my windows PC It's senses it straight away for a bout 10 seconds then drops it... It then senses it again and stays connected to my PC.
Windows recognizes it under portable devices as simply "fire" and an empty explorer window pops up, if I right click on the firestick in windows explorer (it shows as drive) I can pull a properties page which shows its serial number...!
On both my firesticks I have modified my build.prop for a faster boot which doesn't show the splash screen.
Both sticks were modified identically about a month ago and once setup had nothing added to them. They just get used for Kodi and catch-up TV apps.
I root them so as to boot directly into Kodi and freeze the bloat.
Both sticks have been rebooted multiple times.. This one failed after a powercut...
I been reading in the main rooting thread and have come across something about sticks not booting properly due to dm_verity failing and having to flash magisk before (or after... I'm not sure) the image flash.
I'm still reading through the thread so haven't tried anything yet... When i get head round what it is, I'll try.
The other 2 ideas I thought to try was to
1) flash an image directly from the bootloader (if possible.. I need to find more info on this) and
2) taking a backup of the working stick and trying that (It's in use a lot... due to #TotalLockdown! we're at 4 weeks with heavy police curfew! So I haven't had access to it)
If have any ideas or thoughts... I would be very grateful. Also I'm happy to try anything...
Click to expand...
Click to collapse
It's really strange. Usually these steps should fix the issue :
1) Factory Reset from TWRP
2)Wipe System from TWRP
3) Flash full stock (non rooted) firmware
Of course, you could try flashing each image with hacked fastboot, or just boot, system and vendor with TWRP, which also have an option (install image) for that.
But you will have to convert system and vendor from sparse (.dat) to . img before being able to flash them.

Wiping these should have taken care of you issue.
"After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal."
What stock did you flash from where?
When you flash stock are there any errors?
You should be able to take a backup from you other one also for other one (if you are doing a full backup/restore, i would wipe data and cache after restore)

Thanks guys for the replies, I couldn't respond earlier due to an 8 hr powercut today!
Pretoriano80 said:
It's really strange. Usually these steps should fix the issue :
1) Factory Reset from TWRP
2)Wipe System from TWRP
3) Flash full stock (non rooted) firmware
Of course, you could try flashing each image with hacked fastboot, or just boot, system and vendor with TWRP, which also have an option (install image) for that.
But you will have to convert system and vendor from sparse (.dat) to . img before being able to flash them.
Click to expand...
Click to collapse
Hi Pretoriano80
Yeah... It's really weird... I'm starting to think that the stick is damaged in some way, although the fact I can get in both the hacked bootloader and TWRP confuses me!
I've even wiped each partition 3 or 4 times (and rebooted back into recovery to remount) before writing the new image just to make sure.!
I'm ready to try anything at this point, since the stick is a brick at this point.
I'm not really sure how or what to flash from the bootloader, I'll read up a bit before I try especially your tips about converting from sparse to .img.
(I may have some further questions for you, if that's alright )
I will try to restore a backup from another stick first (if I can get access to that stick for long enough...)
Michajin said:
Wiping these should have taken care of you issue.
"After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal."
What stock did you flash from where?
When you flash stock are there any errors?
You should be able to take a backup from you other one also for other one (if you are doing a full backup/restore, i would wipe data and cache after restore)
Click to expand...
Click to collapse
Hi Michajin
Thanks again for taking the time to reply... much appreciated...
I have tried this stock image update-kindle-mantis-NS6271_user_2493_0003590962564
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4059777
as well as a update-kindle-mantis-NS6268_user_2315_0003255372676 image (stock that I think i got from the main rooting thread)
I've also used Rboxes pre-rooted image mantis-6.2.6.8-rooted_r1
which was the image that worked fine on both boxes...
I'm happy to try any other image that you might have a link for.....
When I wipe the partitions there are no errors, except for when I wiped the storage partitions - they did throw up an error - although at this point I had already tried flashing new images at least a dozen times,
All the images flash without error as well!
I'm stumped... I've never had any android device brick before... (soft bricks many times! but never a hard brick), and it's weird since I have access to both the bootloader and TWRP.
Tomorrow I'll be able to get a restore image from the other stick, Then I'll try flashing from bootloader..
The only other thing i thought to try was to crack the case open and redo the the whole root procedure from scratch...

Sorry to double-post...
However I wanted to add this as a separate post rather than an edit.
After playing with my firestick for a few days, during which I tried a working backup and erasing from the bootloader and then restoring multiple images (stock and prerooted), as well running the exploit again.
I realised that the OS was loading (I regained ADB after the full restore) despite not giving an image over HDMI (just a black screen).
I was about to give up when I happened to be going through the options in ADBLink and I found the screenshot button.
I gave it a try and to my surprise it sent back an image of the stick with a working OS/screen.
I even manged to navigate through the settings and do a full reset from within FireOS by taking screengrabs.
After the reset it still gave a black screen, I re-enabled ADB from TWRP and was able to verify that it had reset correctly...
From ADB I ran a logcat...
I'm not really familiar with logcat but a couple of things seemed to jump out...
Code:
1) 596 617 I DisplayManagerService: Display device changed: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 720 x 480, modeId 4, defaultModeId 1, supportedModes [{id=1, width=1920, height=1080, fps=60.000004}, {id=2, width=1920, height=1080, fps=59.94}, {id=3, width=720, height=576, fps=50.0}, {id=4, width=720, height=480, fps=60.000004}], colorMode 0, supportedColorModes [0], HdrCapabilities [email protected], density 320, 213.0 x 216.0 dpi, appVsyncOff 1000000, presDeadline 16666666, touch INTERNAL, rotation 0, type BUILT_IN, state ON, FLAG_DEFAULT_DISPLAY, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
2) 1145 1145 I AmazonHdmiServiceManager: resolution applied and hdmi turned off
3) 596 2438 E AmazonHdmiService: Settings client binder died.
Seeing that there were some issues with the HDMI display (Display device change to built-In screen? and HDMI turned off?), I used the screengrab to navigate my way to display settings which wouldn't allow me to change resolution
So to sum it up...
Everything is loading and running correctly, however I can't get an image over HDMI only by getting screengrabs via ADBlink.
Maybe something on the chip (HDMI output) is damaged, I've had the stick for a while and it's had heavy usage, or something has stuck in a toggled state.
I don't know....
If anyone has any ideas how to test it I have full root access via TWRP and probably can get it over ADB, so any help or commands to try would greatly appreciated....
Thanks :good:

tinybilbo said:
Sorry to double-post...
However I wanted to add this as a separate post rather than an edit.
After playing with my firestick for a few days, during which I tried a working backup and erasing from the bootloader and then restoring multiple images (stock and prerooted), as well running the exploit again.
I realised that the OS was loading (I regained ADB after the full restore) despite not giving an image over HDMI (just a black screen).
I was about to give up when I happened to be going through the options in ADBLink and I found the screenshot button.
I gave it a try and to my surprise it sent back an image of the stick with a working OS/screen.
I even manged to navigate through the settings and do a full reset from within FireOS by taking screengrabs.
After the reset it still gave a black screen, I re-enabled ADB from TWRP and was able to verify that it had reset correctly...
From ADB I ran a logcat...
I'm not really familiar with logcat but a couple of things seemed to jump out...
Code:
1) 596 617 I DisplayManagerService: Display device changed: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 720 x 480, modeId 4, defaultModeId 1, supportedModes [{id=1, width=1920, height=1080, fps=60.000004}, {id=2, width=1920, height=1080, fps=59.94}, {id=3, width=720, height=576, fps=50.0}, {id=4, width=720, height=480, fps=60.000004}], colorMode 0, supportedColorModes [0], HdrCapabilities [email protected], density 320, 213.0 x 216.0 dpi, appVsyncOff 1000000, presDeadline 16666666, touch INTERNAL, rotation 0, type BUILT_IN, state ON, FLAG_DEFAULT_DISPLAY, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
2) 1145 1145 I AmazonHdmiServiceManager: resolution applied and hdmi turned off
3) 596 2438 E AmazonHdmiService: Settings client binder died.
Seeing that there were some issues with the HDMI display (Display device change to built-In screen? and HDMI turned off?), I used the screengrab to navigate my way to display settings which wouldn't allow me to change resolution
So to sum it up...
Everything is loading and running correctly, however I can't get an image over HDMI only by getting screengrabs via ADBlink.
Maybe something on the chip (HDMI output) is damaged, I've had the stick for a while and it's had heavy usage, or something has stuck in a toggled state.
I don't know....
If anyone has any ideas how to test it I have full root access via TWRP and probably can get it over ADB, so any help or commands to try would greatly appreciated....
Thanks :good:
Click to expand...
Click to collapse
Just checking, but have you tried another HDMI cable and different TV? Somehow it is not recognizing the format in the OS. TWRP uses a lower format i believe. I have had a power surge before damaging HDMI here, but I wouldn't get anything with it plugged in.

Michajin said:
Just checking, but have you tried another HDMI cable and different TV? Somehow it is not recognizing the format in the OS. TWRP uses a lower format i believe. I have had a power surge before damaging HDMI here, but I wouldn't get anything with it plugged in.
Click to expand...
Click to collapse
Hi Michajin,
Thanks for your reply...
Yes I have tried multiple TV's, Monitors , and cables... Including the TV that it had been running on for almost a year...
I get frequent powercuts where I live, and often power surges when the power comes back on...
I do use surge protectors, however they don't always work....
One time the electricity board double one of the phases to 440v and knocked out £5k worth of equipment!
So between that and the humidity I think there is some minor damage to the stick... shame because it's still running.
I'm going to see if I can get a logcat from TWRP and see what it says about the HDMI output, not that it'll help...

tinybilbo said:
Hi Michajin,
Thanks for your reply...
Yes I have tried multiple TV's, Monitors , and cables... Including the TV that it had been running on for almost a year...
I get frequent powercuts where I live, and often power surges when the power comes back on...
I do use surge protectors, however they don't always work....
One time the electricity board double one of the phases to 440v and knocked out £5k worth of equipment!
So between that and the humidity I think there is some minor damage to the stick... shame because it's still running.
I'm going to see if I can get a logcat from TWRP and see what it says about the HDMI output, not that it'll help...
Click to expand...
Click to collapse
So you get a display in TWRP, but go black after booting? I wonder if you can force whatever display mode and setting as used in TWRP as your display mode in FireOS. Had you tried another wall outlet (higher mA) ? A long shot at this point that you havent tried it....

Michajin said:
So you get a display in TWRP, but go black after booting? I wonder if you can force whatever display mode and setting as used in TWRP as your display mode in FireOS. Had you tried another wall outlet (higher mA) ? A long shot at this point that you havent tried it....
Click to expand...
Click to collapse
Correct, I can get a display with TWRP, but it goes black when it boots into FireOS (from which I can get screengrab via adblink of the stick displaying FireOS or whatever app is running).
Up until now (for almost a year) I've just used the power adapter that came with the stick, but it's a good idea to try something more powerful (I have a 2.4a one that I'll try a little later).
Another thing I'm going to try is "adb shell wm size ***x***" "adb shell wm density ***" command to change the resolution & pixel density (I think).
I hadn't thought about power being an issue up until you mentioned it (because so far it hasn't been), but maybe a component has (or is) failed (or failing) so it might need more power...
I can't try until a little later this evening, but at least I have something to try now cheers! I'll let you know how I get on....

tinybilbo said:
Correct, I can get a display with TWRP, but it goes black when it boots into FireOS (from which I can get screengrab via adblink of the stick displaying FireOS or whatever app is running).
Up until now (for almost a year) I've just used the power adapter that came with the stick, but it's a good idea to try something more powerful (I have a 2.4a one that I'll try a little later).
Another thing I'm going to try is "adb shell wm size ***x***" "adb shell wm density ***" command to change the resolution & pixel density (I think).
I hadn't thought about power being an issue up until you mentioned it (because so far it hasn't been), but maybe a component has (or is) failed (or failing) so it might need more power...
I can't try until a little later this evening, but at least I have something to try now cheers! I'll let you know how I get on....
Click to expand...
Click to collapse
Hey I have a debloated clean stable rom that will be available soon. You can try that and you need to be sure to have either a usb otg or a hub for transferring this backup which will be titled ftvs4kdebloatedv1.0. Paste this folder to TWRP/BACKUPS/YOUR SERIAL #/ftvs4kdebloatedv1.0.

Skel40 said:
Hey I have a debloated clean stable rom that will be available soon. You can try that and you need to be sure to have either a usb otg or a hub for transferring this backup which will be titled ftvs4kdebloatedv1.0. Paste this folder to TWRP/BACKUPS/YOUR SERIAL #/ftvs4kdebloatedv1.0.
Click to expand...
Click to collapse
Thanks Skel40
I'll definitely give the clean rom a go
I have an OTG & Hub and the serial number already

hi guys
i have a firestick 2th gen model ly78pr its brick stock on logo , the problem is usb debbug was off and i tried with the key board and otg cable pressing alt + printscreen + i and it does not work as , i tried different combination and nothing help , also i connected to the pc and it does not work with adb it doesnt reconize , if anyone can help to find any solution