Develop Bugs

BOOTLOOPS GALORE! help :(

Hey guys,
glad to say that ive been able to debrick my phone like 5 times in a row successfully which is a weight off my shoulders.
however, once im debricked, rooted, cwm installed, and all .img's pushed i try to flash a custom rom. i've tried every one and i get bootloops every time... they seem to install just fine. very normal timing and everything, no errors. any ideas?

Don't format /data. Are you doing that? Link the steps you're taking when you are in cwm to flash over the rom. Maybe something is amiss.

nope not formatting data. ive been doing wipe cache, wipe dalvik, and format /system.

Man I was in the same boat as you but was finally able to get it sorted this morning. What I highly, highly recommend is starting as fresh and as clean as you possibly can. That is before you do CWM or anything like that restore your phone with the Korean kdz, push all the images (system being last) then make sure you have a bootable, working phone. Also I would recommend using different/new/fresh .img files...I downloaded ones from the unbricking thread and only used a copy of my baseband.img. I had a feeling one of my files wasn't quite right so starting with all new ones may have helped.
Don't try anything from a backup or do a restore or anything-start fresh and make sure everything works as it should. From there do CWM and then do your ROMS. I know you're almost there and its a headache to keep starting from the bottom but do it all one step at a time, in order and you will find success.
Good luck!

good call. i havent been pushing all the .img's. just the three he mentioned above. let me try this for the 80th time. ill let you know how it goes. just curious, do you use the v10f or v10i kdz?

Are the ROMs installing in less than 30 seconds or 2-5 minutes? If its less than 30 seconds, you need to flash it again.

If i was you i would install the new CWM, once it installs the new CWM it'll work.

gte460z said:
Are the ROMs installing in less than 30 seconds or 2-5 minutes? If its less than 30 seconds, you need to flash it again.
Click to expand...
Click to collapse
yep i know that part. thanks
Revolution said:
If i was you i would install the new CWM, once it installs the new CWM it'll work.
Click to expand...
Click to collapse
new cwm?? as in the newest version available?does it work on the nitro?

[CWM][24/01] ClockworkMod 5 Recovery For LG Nitro HD
http://forum.xda-developers.com/forumdisplay.php?f=1448
Follow instruction's then try flashing a ROM it should fix your problem.

ive been using cwm... doesnt get rid of the bootloops

mic.mayorga said:
ive been using cwm... doesnt get rid of the bootloops
Click to expand...
Click to collapse
I'm not sure you understand bro, there is a NEW UPDATE
Update your CWM and it'll fix this issue.

I had the same problem for awhile. Had to use the Unbricker:http://forum.xda-developers.com/showthread.php?t=1412367
Followed ALL instructions, including "Restoring Nitro HD partition images" before flashing CWM. After that, no more bootloops and installed Revolutions rom w/out issue. Reboots just fine after.

I used the V10i-the direct download from LG...I think all the other recommendations are spot on but first and foremost get everything squared away with a fresh install of the kdz, all the images (in the proper order), the new version of CWM and then your rom of choice...Hope you're making some progress!

I'm on the new CWM and still have a loop if I reboot. Then I need to restore from CWM to get going again.
The soft brick boot loop I got was caused solely by format /system. I did not format /data.

I went through the whole deal last night and this morning and was able to get a fresh start on everything and am now running the HD ROM and haven't had a boot loop since I got everything back up and running...
I really think starting with the freshest install and making sure everything is functional step by step is where you'll be able to get through all that mess...just stay away from and restores or using any .img files that may have any software glitches as you'll get back to square one every time.
Hope you get it sorted out!

nah bro, i had the new update. no worries tho i pushed all the images in the debrick and fixed it. thanks for all the help guys B)

Tight work-glad you were able to get it straight! Now once you get it where you want make a new backup with Nandroid and CWM and you'll be golden in case anything else happens.

Hi all,
I'm in a boot loop too, so may I ask you guys a stupid question:
How to restore the previous system.img?
Thanks

huydq5000 said:
Hi all,
I'm in a boot loop too, so may I ask you guys a stupid question:
How to restore the previous system.img?
Thanks
Click to expand...
Click to collapse
Go look at the thread "[Solved] Unbricking solution...". Follow it to the T, however, i'd recommend using v10i.kdz rather than v10f.kdz. Definitely try the f version first but if it doesn't work try i. That's what I did. Basically what you're going to want to do is:
1. Restore the phone to a korean image using the v10i (or f) file and the LG software provided and referenced in the unblocking thread.
2. Once booted, root the phone. (specific instructions for v10i are in a thread somewhere linked by [email protected] v10f use either SuperOneClick root or DoomLord v4. Make sure you have adb installed for doomlord.
3. Once rooted use adb to push over stock .img files in this order: boot, recovery, firmware, baseband, system.
4. after the files are pushed boot into phone and root again (optional).
5. Install CWM5 through adb or terminal emulator.
Good luck, let me know if you have any questions and I can go into more detail.

Odd Kindle / Jelly Bean / Gapps issue

Recently put Jelly Bean on my Kindle - JB flashed, using TWRP, fine and runs great. Gapps will NOT flash, no matter which I use; it fails using TWRP each time, even after clearing cache and even redoing the whole install process.
I figured I would just sideload the Google Play store and any others I needed, but Google Play will not open once installed; it pops open for a split second then closes. I read that installing Talk and signing in would fix this, but after sideloading Talk it does the same thing.
So it seems no Google apps will sideload properly and I also am unable to flash any gapps.zip's.
Any idea? Did I miss something obvious?

Depends...are you using the CM10 gapps?
Also, what version of TWRP are you using?

Yes, CM10 (tried others too) and TWRP 2.

sleep_debt said:
Yes, CM10 (tried others too) and TWRP 2.
Click to expand...
Click to collapse
2.0? 2.1? 2.2?
Also, are you checking the md5s? It's a longshot but worth looking into.

Which version of gapps are you using?

TWRP 2.2 is what I'm using.
Not sure the gapps versions, but ive tried about 5 different ones. All from July and August.
What would I be checking in the md5's exactly?

sleep_debt said:
TWRP 2.2 is what I'm using.
Not sure the gapps versions, but ive tried about 5 different ones. All from July and August.
What would I be checking in the md5's exactly?
Click to expand...
Click to collapse
Make sure it's this version.
http://goo.im/gapps/gapps-jb-20120726-signed.zip
Sent from my Nexus 7 using Tapatalk 2

TWRP 2.2 is still quite new and it is yet unknown of all the bugs that may come with it. Have you tried an earlier version?

Did you find a solution to your problem yet?
sleep_debt said:
Recently put Jelly Bean on my Kindle - JB flashed, using TWRP, fine and runs great. Gapps will NOT flash, no matter which I use; it fails using TWRP each time, even after clearing cache and even redoing the whole install process.
I figured I would just sideload the Google Play store and any others I needed, but Google Play will not open once installed; it pops open for a split second then closes. I read that installing Talk and signing in would fix this, but after sideloading Talk it does the same thing.
So it seems no Google apps will sideload properly and I also am unable to flash any gapps.zip's.
Any idea? Did I miss something obvious?
Click to expand...
Click to collapse
Hi sleep_debt, I was wondering if you have found a solution to this problem yet. I am also having a problem getting access to Google Play. I've tried loading multiple versions of GoogleServicesFramework.apk and Vending.apk, etc. I am able to get them to install, but when I open the "Market" icon it prompts me to create an account and sign in, but it is never able to make the connection. I am also confused by references to the "Google Play" store. I don't have anything called "Google Play" I only have an icon called "Market". So, I think I'm missing something, but I don't know what.
Val

vmallder
vmallder said:
Hi sleep_debt, I was wondering if you have found a solution to this problem yet. I am also having a problem getting access to Google Play. I've tried loading multiple versions of GoogleServicesFramework.apk and Vending.apk, etc. I am able to get them to install, but when I open the "Market" icon it prompts me to create an account and sign in, but it is never able to make the connection. I am also confused by references to the "Google Play" store. I don't have anything called "Google Play" I only have an icon called "Market". So, I think I'm missing something, but I don't know what.
Val
Click to expand...
Click to collapse
Which ROM did you use? The two ROMs I have tried both had an accompanying gapps zip file. I'm using TWP installed by KFU 0.9.6. I installed cm-10 from sgt7-linaro and jdaycane 1.7.2. I flashed the gapps ROM at the same time using TWRP and had no issues.

vmallder said:
Hi sleep_debt, I was wondering if you have found a solution to this problem yet. I am also having a problem getting access to Google Play. I've tried loading multiple versions of GoogleServicesFramework.apk and Vending.apk, etc. I am able to get them to install, but when I open the "Market" icon it prompts me to create an account and sign in, but it is never able to make the connection. I am also confused by references to the "Google Play" store. I don't have anything called "Google Play" I only have an icon called "Market". So, I think I'm missing something, but I don't know what.
Val
Click to expand...
Click to collapse
nmaiorana said:
Which ROM did you use? The two ROMs I have tried both had an accompanying gapps zip file. I'm using TWP installed by KFU 0.9.6. I installed cm-10 from sgt7-linaro and jdaycane 1.7.2. I flashed the gapps ROM at the same time using TWRP and had no issues.
Click to expand...
Click to collapse
Not sure what this issue is, still - have tried every gapps & TWRP version I could find, but TWRP also throws an error when trying to flash gapps.
Also, sideloading the gapps just doesnt work, either, making me think the actual OS flash might be damaged? Been busy lately but plan on just flashing another OS and seeing if that clears it up.
If anyone has any other tips, it would be much appreciated!

Update:
Spent the weekend trying to re-root, flash Jellybean/Gapps to no avail. Same results (when Jelly bean is installed, Gapps will not flash using TWRP 2.2.2). I then wiped everything, leaving only TWRP. Cleared all caches, etc and tried to re-flash Jellybean; now NOTHING will flash successfully and there is no OS anymore, just TWRP.
How can I get an OS back on if TWRP isnt cooperating?

What errors do you get when trying to flash gapps or ROMs?

sleep_debt said:
Update:
Spent the weekend trying to re-root, flash Jellybean/Gapps to no avail. Same results (when Jelly bean is installed, Gapps will not flash using TWRP 2.2.2). I then wiped everything, leaving only TWRP. Cleared all caches, etc and tried to re-flash Jellybean; now NOTHING will flash successfully and there is no OS anymore, just TWRP.
How can I get an OS back on if TWRP isnt cooperating?
Click to expand...
Click to collapse
i would try adb installing twrp 2.2.2.1 and then flashing a rom, i read that the update fixed some issues that your probably having.

callmeshulah said:
i would try adb installing twrp 2.2.2.1 and then flashing a rom, i read that the update fixed some issues that your probably having.
Click to expand...
Click to collapse
That's the version of TWRP I'm using; the error I'm getting when flashing anything is:
* Verifying filesystems...
* Verifying partition sizes...
Error flashing zip 'whateverthefileis.zip'

TWRP errors
I agree with nmaiorana, cm-10 from linaro is not throwing errors like you seem to be running into. Latest version I am using is: 10-20120831-2228. the gapps v that works with this rom is: gapps-jb20120726. In TWRP after clearing cache and dalvik cache, goto to Install, click on the ROM you want to install, then go back to install and click on the gapps file, then slide the button to the right. You can install multiple flash files this way in TWRP. See if that works.
[email protected]@dog

If you've tried reinstalling every version of TWRP and you have tried installing different ROMs and they all return the exact error you posted, try this:
fastboot oem format
...and then reinstall TWRP. If that doesn't work, fastboot may not be working to correctly flash information to the recovery partition. If that's the case you may need to replace your bootloader, but not with fastboot. TWRP probably wouldn't work either and you don't want to open the case to do the shorting trick unless you have to.
My suggestion would be to use adb to install TWRP and see if that makes a difference. If that works and you can flash ROMs normally, replace your bootloader right away.
At least that's what I would try.

Pull the recovery log and see if it gives you more details on what's causing the flash to fail...
Attempt to install the gapps package. After it fails, run the following adb command
Code:
adb pull /cache/recovery/last_log recovery_log.txt
You'll find the recovery_log.txt file in your current working directory. Copy and paste the contents of the log file into pastebin.com and share the URL here.

soupmagnet said:
If you've tried reinstalling every version of TWRP and you have tried installing different ROMs and they all return the exact error you posted, try this:
fastboot oem format
...and then reinstall TWRP. If that doesn't work, fastboot may not be working to correctly flash information to the recovery partition. If that's the case you may need to replace your bootloader, but not with fastboot. TWRP probably wouldn't work either and you don't want to open the case to do the shorting trick unless you have to.
My suggestion would be to use adb to install TWRP and see if that makes a difference. If that works and you can flash ROMs normally, replace your bootloader right away.
At least that's what I would try.
Click to expand...
Click to collapse
kinfauns said:
Pull the recovery log and see if it gives you more details on what's causing the flash to fail...
Attempt to install the gapps package. After it fails, run the following adb command
Code:
adb pull /cache/recovery/last_log recovery_log.txt
You'll find the recovery_log.txt file in your current working directory. Copy and paste the contents of the log file into pastebin.com and share the URL here.
Click to expand...
Click to collapse
will try these in the next few days and see if anything works.
btw, ive tried every recent rom/gapps with no luck, so it doesnt seem to be a version-issue.

TWRP Help. v2.2.2.1

Hi. So I consider myself somewhat of an amateur now at ROMing and messing with the Kindle Fire ecosystem, but lately I have been having trouble. I have the latest TWRP (I think) installed. I am using twa_priv's latest builds of Jellybean on a weekly basis, but am switching a bit back and forth between that and the stock 2.3 KF system because that supports a few things that Jellybean hasn't covered yet. My problem is that when I create a backup...it seems to create one just fine. BUT when I try to restore the backup, it "runs" the backup in about 10 seconds, and when I go to reboot the system, it warns me that no OS i installed.
What is my problem?

Josepho1997 said:
Make sure you select all of he options for restore(system, data, cache, ect.)
Android>iOS... Android FTW!
Click to expand...
Click to collapse
Thanks for the advice. However, I have made sure to do that every time. I have messed with all the settings I can think of. Including the md5 file properties. Hopefully this picture of the files from one of my more recent backups helps?

jma9454 said:
Thanks for the advice. However, I have made sure to do that every time. I have messed with all the settings I can think of. Including the md5 file properties. Hopefully this picture of the files from one of my more recent backups helps?
Click to expand...
Click to collapse
Run the restore as you have been. Pull the recovery log...
Code:
adb pull /cache/recovery/last_log recovery_log.txt
Put it up on pastebin and post the URL here.

kinfauns said:
Run the restore as you have been. Pull the recovery log...
Put it up on pastebin and post the URL here.
Click to expand...
Click to collapse
OK. so here is the link. I don't understand it one bit, so hopefully you can make something out of it.
http://pastebin.com/TBVU1Lhu

jma9454 said:
OK. so here is the link. I don't understand it one bit, so hopefully you can make something out of it.
http://pastebin.com/TBVU1Lhu
Click to expand...
Click to collapse
Well, I thought TWRP would write to the log file with some details on its restore operations, but it apparently does not. My bad for making you jump through those hoops needlessly.
I would try deleting or renaming the TWRP folder in /sdcard, rebooting back into TWRP, and trying the backup/restore process again. If that doesn't help, try reflashing TWRP and repating the process with different ROMs, I don't believe this is a known problem with TWRP, so you have to try narrowing down the variables and seeing what helps.

kinfauns said:
Well, I thought TWRP would write to the log file with some details on its restore operations, but it apparently does not. My bad for making you jump through those hoops needlessly.
I would try deleting or renaming the TWRP folder in /sdcard, rebooting back into TWRP, and trying the backup/restore process again. If that doesn't help, try reflashing TWRP and repating the process with different ROMs, I don't believe this is a known problem with TWRP, so you have to try narrowing down the variables and seeing what helps.
Click to expand...
Click to collapse
OK, thanks. I am going to try reinstalling TWRP. I have tried most of the helpful hints that you have given me already, so I figure that maybe my TWRP is bad? I forgot to mention that I came from CWM because I originally had TWRP, switched to CWM, hated it, and reinstalled TWRP through the KFU.
I got a flashable TWRP from this link:
http://forum.xda-developers.com/showthread.php?p=30780737
The only problem is that I don't know the adb command to flash TWRP onto the kindle. Any help?

jma9454 said:
OK, thanks. I am going to try reinstalling TWRP. I have tried most of the helpful hints that you have given me already, so I figure that maybe my TWRP is bad? I forgot to mention that I came from CWM because I originally had TWRP, switched to CWM, hated it, and reinstalled TWRP through the KFU.
I got a flashable TWRP from this link:
http://forum.xda-developers.com/showthread.php?p=30780737
The only problem is that I don't know the adb command to flash TWRP onto the kindle. Any help?
Click to expand...
Click to collapse
That zip archive needs to be installed with TWRP like you would a ROM. I suggest you set that aside and install it the old fashioned way and use fastboot...
http://forum.xda-developers.com/showthread.php?t=1638452

[Q] 4.2 Upgrade Problems-- verizon gnex

My vzw nexus has been running mRom version x.x for sometime. I went to install the upgraded 4.2 rom via clockworkmod, (wipe cache and dalvik, flash over current rom) and it appeared to install successfully. However, when I rebooted I saw the lock screen for a split second and it just started to boot loop. I rebooted back into recovery and wiped all data and tried to reinstall the rom via through the new 0 partition, but I get the error symlink: some symlinks failed
E: Error in /sdcard/0/mRom_v3.0_JOP40C.zip (status 7)
I think that this may have something to do with the multiple users in 4.2, but don't quote me on it. I cannot get my computer to recognize my phone, when I go to mounts in cwm I can mount everything except the sdcard, although I think this problem was evident before I flashed. Any suggestions? I could try to restore to stock using galaxynexusrestore-- http://forum.xda-developers.com/showthread.php?t=1743939 but I have not tried it before so I cannot speak to weither it will work or not.
HELP!

Always always wipe data when changing an Android version. Unless it comes via OTA, which is specifically designed to fix all the little problems that will arise.
As to how to fix the problem, flashing a factory image
http://forum.xda-developers.com/showthread.php?t=1626895 will probably work. Just follow the rules for Toro. The toolkit you linked may work, but it's generally a better idea to not use them and actually familiarize yourself with how to fix things yourself, you'll be less likely to make mistakes in the future.

Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!

Misread OP.

ironerd said:
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Click to expand...
Click to collapse
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.

same problem, stuck at JB logo
Marisa said:
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
Click to expand...
Click to collapse
I was running stock JRO03O with Clockwork Recovery Mod and decided to flash the JB 4.2 ROM from Grouper (http://forum.xda-developers.com/showthread.php?t=1993545 - I can't post there since I'm too new).
The update must have succeeded, because I can see the new 0/ partition on my phone, but it won't boot past the "X" logo. I can boot into CWM and try various things, but of course because of the data structure changes, I can't actually recover to my last save. When I'm home, I'm hoping I can get the CWM backup off my phone to restore later, but without a terminal in CWM, I can't try to fix the path.
It's nice to hear that CW is working on a fix - I hope it's retroactive (I mean, helpful to those of use who already screwed up). Also, I've never flashed anything but OTA, so I didn't realize I needed to wipe data before flashing something that's supposed to be almost stock. I guess it matters how different from stock the ROM actually is.
What's next? I'll try to interface with my PC at home. If others have this problem, I'd be happy to hear your success (or fail) stories. I'll share mine once I've tried it.

The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Koush
When trying to restore CWM backup move previous backups AND blobs folder to /data/media/clockworkmod if the folder does not exist simply create one or if unsure just go to recovery and make new backup, it will create necessary folders for you then move (or copy to be safe) files to location.... The blobs folder is what I was missing and why I kept getting error while trying to restore.
Click to expand...
Click to collapse
This should help your problem solving for the moment, if you're familiar enough with ADB to move the files that way it shouldn't take very long at all

thanks, and update of my status
Marisa said:
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Click to expand...
Click to collapse
Thanks for the extra insight. I wrestled with my phone all night and finally got it back to 4.1.1 (JRO030). Along the way I screwed up my adb or fastboot drivers, and for all my efforts I couldn't get any of my nexus toolkits to recognize the phone as in fastboot mode. Adb was fine, but fastboot was a no-go. I moved to a fresh computer after someone else had success with that, and read up on how to do a manual (adb command line) flash to factory image.
Now that that's done, I'm hoping I can restore from CWM to get back to where I was. If not, then yuck, but I'm optimistic.

Fire TV 4k not possible to set up

Hello,
i've had this issue with the stock firmware so i thought installing twrp with a prerooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.

Retch_100 said:
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a prerooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Click to expand...
Click to collapse
A Lineage OS rom is still under development and not released yet. Have you tried flashing the stock image (6.2.7.1)? Flash this in recovery, to see if it fixes the update error. You may need to flash Magisk to be rooted again. And this stock image WILL NOT overwrite TWRP. The prerooted roms that are released have Magisk built in so there's nothing different between those and the stock image in which has no root at all. Let me know if you have any questions!
Stock Image for Fire TV Stick 4K: https://drive.google.com/open?id=1LlOFUO8o_8GKm-kQLR9QCMmql2Zyu8W8

Retch_100 said:
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a pre-rooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Click to expand...
Click to collapse
From what I have seen, the tutorial for flashing the prerooted is really a dirty flash, and certainly from my experience (where I forgot to reset the device before flashing the image) all my apps were still there.
I'm sure you can wipe your system & data partition from TWRP, and then flash the image.
The only problem I can foresee is that the pre-rooted image might not be a full image which would cause your Firestick not to boot.
I suggest you head over to the pre-rooted image thread and ask if it's ok to wipe those partitions and also what the actual commands are.
I'm curious also - just for future reference....
p.s I just found this
https://twrp.me/faq/openrecoveryscript.html
which lists TWRP's commands, Just check first to see if it's safe to wipe those partitions.

Okay, i will install it tomorrow. Is there a Source to the lineage Development? The Stick is unusable for me, so i Would install anything to Pass the error.
@tinybilbo
Good question, i didnt Know Either what to do so i Wiped cache and dalvik and data, but That should be considered as a Dirty Flash thought, i will ask there.
@Skel40
What to Wipe before flashing?

Retch_100 said:
Okay, i will install it tomorrow. Is there a Source to the lineage Development? The Stick is unusable for me, so i Would install anything to Pass the error.
@tinybilbo
Good question, i didnt Know Either what to do so i Wiped cache and dalvik and data, but That should be considered as a Dirty Flash thought, i will ask there.
@Skel40
What to Wipe before flashing?
Click to expand...
Click to collapse
I think the system partition would be the important one to wipe, data is mostly user data from what I remember.
If Skel40's link is a full image (as the prerooted one i might be), then maybe do all the wipes and try that one 1st..
Normally when I use TWRP I don't dirty flash, and I wipe system,data,dalvik,cache...
Good luck with whatever you try

Retch_100 said:
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a prerooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Click to expand...
Click to collapse
Retch_100 said:
Okay, i will install it tomorrow. Is there a Source to the lineage Development? The Stick is unusable for me, so i Would install anything to Pass the error.
@tinybilbo
Good question, i didnt Know Either what to do so i Wiped cache and dalvik and data, but That should be considered as a Dirty Flash thought, i will ask there.
@Skel40
What to Wipe before flashing?
Click to expand...
Click to collapse
You need to wipe system, data, dalvik-cache, and cache before flashing. Upon boot up after flashing 6.2.7.1, it skips the updates, I have a backup if needed!

I wiped all Partitions and Flashed the Image, but it searches for backups and the error appears. Could you send me the Backup? @Skel40

Retch_100 said:
I wiped all Partitions and Flashed the Image, but it searches for backups and the error appears. Could you send me the Backup? @Skel40
Click to expand...
Click to collapse
You wiped everything (data, system, internal, cache, dalvik). There is nothing else, if you are flashing the full stock upgrade image. The device finds remote, connects to bluetooth, then finds Wifi, connects to wifi. Then the device errors (when checking for an update). Since you bought this device used, i highly suspect the device is blacklisted. Firestick 4k's are on sale for $25 again. I would cut my loses and hope someday for a custom (you can ask for a copy of the buggy one diegocr and Rortiz2 over in the tank 12.1 thread. But it is likely unusable at this time.

Okay thank you @Michajin
What do you think, would be installing TWRP on one of the others and restoring a backup from them onto the broken one help?

Retch_100 said:
Okay thank you @Michajin
What do you think, would be installing TWRP on one of the others and restoring a backup from them onto the broken one help?
Click to expand...
Click to collapse
I don't think so. I believe it is sending its serial number to amazon when it connects to the internet. There used to be a work around that would bypass registration, but i believe that was blocked about a year ago. Maybe someone on here knows a work around since you have access with TWRP (file manager), If it were me, i would find the update files in TWRP and rename or delete them... i think they are in the root/system folder. Since you have a full backup i dont see much risk. If it fails to boot or work, just restore your system from a backup.
The files should be called:
device.software.ota
com.amazon.device.software.ota.override

Michajin said:
I don't think so. I believe it is sending its serial number to amazon when it connects to the internet. There used to be a work around that would bypass registration, but i believe that was blocked about a year ago. Maybe someone on here knows a work around since you have access with TWRP (file manager), If it were me, i would find the update files in TWRP and rename or delete them... i think they are in the root/system folder. Since you have a full backup i dont see much risk. If it fails to boot or work, just restore your system from a backup.
The files should be called:
device.software.ota
com.amazon.device.software.ota.override
Click to expand...
Click to collapse
Okay thanks I will see.
BTW: the Stick does not have any value to me anymore, so bricking it would be okay if I learned something this way
But it'd be better if the Stick could be resurrected to work as a Stick.

Maybe anything of this.
Pass OOBE:
==========
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
adb shell settings put secure install_non_market_apps 1
adb shell settings put global adb_enabled 1
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
pm disable com.amazon.tv.oobe

Your fire stick blacklisted by Amazon.