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.
so i recently dove into rooting my s4 after first spending a lot of time reading this great board, thought i had a handle on it, thought things were going very well, but i've hit a snag, which came while attempting my first restore - i'm hopeful someone will give me a little help,
a little background:
1. before rooting i backed up my phone with titanium, also backed it up by copying all of its contents to my pc.
2. i followed the excellent "[SGH-M919] CF-Auto-Root" instructions and it worked without a hitch, it was a quick and easy process, no surprises.
3. confirmed that i was rooted using "root checker", all systems were go.
4. once the root was done i made another backup using titanium and sms backup. i also made a full system backup using online nandroid pro and, to be extra safe, i also backed up efs using efs backup tool.
5. i then moved some folders and files to my external card and once again backed up my phone as before, including to my pc.
6. feeling confident that i could now restore my system to its rooted stock state if things went south, i decided to flash my first rom with cwm, i went with cm11 m7 4.4.3 - i saved the cm11 and gapps zips to my external card using rom tool box pro, rebooted into cwm recovery, selected the two files, and flashed. i also did a data and cache wipe before doing so.
6. needless to say i was thrilled when cm11 loaded perfectly, it worked great, and it was just what i was hoping for.
7. having been bitten by the apparent ease of flashing roms, i decided to restore my system to it's pre cm11 state, to it's rooted stock rom state, and try another rom, rather than just flash another rom from cm11 - i wanted to make sure that returning to my rooted stock rom state would be a simple matter.
and that's where i've run into problems.
1. as i mentioned i made two system backups of my stock rom before flashing cm11, one right after i rooted my phone, and one after moving some folders and files to the external card.
2. after doing a wipe, i chose to restore the second backup, the one i made after moving files and folders, and it didn't quite work out - everything appeared to restore perfectly, but my device was immediately inundated with pop up warnings about stopped apps, i also got a persistent warning that the system had stopped responding as well, prompting me to choose between "wait" or "stop it". not only was the restored backup mired in popup screens, but it was impossibly slow, impossibly "laggy".
3. so i decided to restore the other stock backup, the one i made before i moved folders and files, and the results were the same, pop screens for apps not working, system warnings, severe lags, etc., identical to the first backup.
then i panicked.
1. i decided to flash my phone with the "[SGH-M919] CF-Auto-Root" file again, again with odin, hoping that it would put me where i started - i didn't stop to think that my phone was already rooted, that the file was was for unrooted phones.
2. not only did the reflash not work (my phone just booted as normal, as if the flash didn't get a chance to finish), but cwm recovery in boot mode was gone, replaced by what appears to be the andorid stock recovery screen, a screen with an animated dying/collapsing robot, - the screen was titled: "android system recovery <3e> and asked for an "update" from the external storage or cache.
3. not knowing what "update" it was looking for, i selected a backed system files (the first rooted stock rom backup i made, the second rooted stock backup i made, and even the cm11 file) - none worked.
4. i then downloaded a clean stock rom from cwm's website, converted it from zip to tar, and tried to flash it using odin with my device in upload mode, it didn't work either.
so how badly did i mess up my phone? any help would be greatly appreciated.
aeneas1 said:
so i recently dove into rooting my s4 after first spending a lot of time reading this great board, thought i had a handle on it, thought things were going very well, but i've hit a snag, which came while attempting my first restore - i'm hopeful someone will give me a little help,
a little background:
1. before rooting i backed up my phone with titanium, also backed it up by copying all of its contents to my pc.
2. i followed the excellent "[SGH-M919] CF-Auto-Root" instructions and it worked without a hitch, it was a quick and easy process, no surprises.
3. confirmed that i was rooted using "root checker", all systems were go.
4. once the root was done i made another backup using titanium and sms backup. i also made a full system backup using online nandroid pro and, to be extra safe, i also backed up efs using efs backup tool.
5. i then moved some folders and files to my external card and once again backed up my phone as before, including to my pc.
6. feeling confident that i could now restore my system to its rooted stock state if things went south, i decided to flash my first rom with cwm, i went with cm11 m7 4.4.3 - i saved the cm11 and gapps zips to my external card using rom tool box pro, rebooted into cwm recovery, selected the two files, and flashed. i also did a data and cache wipe before doing so.
6. needless to say i was thrilled when cm11 loaded perfectly, it worked great, and it was just what i was hoping for.
7. having been bitten by the apparent ease of flashing roms, i decided to restore my system to it's pre cm11 state, to it's rooted stock rom state, and try another rom, rather than just flash another rom from cm11 - i wanted to make sure that returning to my rooted stock rom state would be a simple matter.
and that's where i've run into problems.
1. as i mentioned i made two system backups of my stock rom before flashing cm11, one right after i rooted my phone, and one after moving some folders and files to the external card.
2. after doing a wipe, i chose to restore the second backup, the one i made after moving files and folders, and it didn't quite work out - everything appeared to restore perfectly, but my device was immediately inundated with pop up warnings about stopped apps, i also got a persistent warning that the system had stopped responding as well, prompting me to choose between "wait" or "stop it". not only was the restored backup mired in popup screens, but it was impossibly slow, impossibly "laggy".
3. so i decided to restore the other stock backup, the one i made before i moved folders and files, and the results were the same, pop screens for apps not working, system warnings, severe lags, etc., identical to the first backup.
then i panicked.
1. i decided to flash my phone with the "[SGH-M919] CF-Auto-Root" file again, again with odin, hoping that it would put me where i started - i didn't stop to think that my phone was already rooted, that the file was was for unrooted phones.
2. not only did the reflash not work (my phone just booted as normal, as if the flash didn't get a chance to finish), but cwm recovery in boot mode was gone, replaced by what appears to be the andorid stock recovery screen, a screen with an animated dying/collapsing robot, - the screen was titled: "android system recovery <3e> and asked for an "update" from the external storage or cache.
3. not knowing what "update" it was looking for, i selected a backed system files (the first rooted stock rom backup i made, the second rooted stock backup i made, and even the cm11 file) - none worked.
4. i then downloaded a clean stock rom from cwm's website, converted it from zip to tar, and tried to flash it using odin with my device in upload mode, it didn't work either.
so how badly did i mess up my phone? any help would be greatly appreciated.
Click to expand...
Click to collapse
If it boots at all you didn't kill it.
Not sure what rom you got from the CWM site. They do recoveries, not roms. The ROM manager app does allow you to download roms, but you can't just convert those from zip to tar. That doesn't make them flashable in Odin.
Here's what you do. Get the stock ROM from either here on XDA (use the search feature to find it) or from Sammobile.com.
Flash that in Odin.
Then you can start over.
---OR---
If you want to try to fix what you've got now, download CWM or TWRP RECOVERY (nor ROM) and flash that in Odin. Boot to recovery, wipe data and system, and flash any other rom you want. That will start you over with a fresh rom of your choice.
Skipjacks said:
f it boots at all you didn't kill it.
Click to expand...
Click to collapse
hallelujah!
Skipjacks said:
Not sure what rom you got from the CWM site. They do recoveries, not roms.
Click to expand...
Click to collapse
my apologies, i meant that i downloaded recovery files from the cwm website, not a rom files - i got them from https://www.clockworkmod.com/rommanager - i downloaded both (touch & non-touch) s4 t-mobile versions (6.0.4.7). i'm assumed those were recovery files?
Skipjack" said:
The ROM manager app does allow you to download roms, but you can't just convert those from zip to tar. That doesn't make them flashable in Odin.
Click to expand...
Click to collapse
again, my apologies - i meant that i downloaded *.img files, not zips, and converted them to tars for odin use. i used a batch file to convert them from img to tar, found at xda, here: http://forum.xda-developers.com/showthread.php?t=2281287 - it seemed to do the job, odin ran and reported success. wrong files? wrong conversion?
Skipjack said:
Here's what you do. Get the stock ROM from either here on XDA (use the search feature to find it) or from Sammobile.com.
Flash that in Odin.
Then you can start over.
---OR---
If you want to try to fix what you've got now, download CWM or TWRP RECOVERY (nor ROM) and flash that in Odin. Boot to recovery, wipe data and system, and flash any other rom you want. That will start you over with a fresh rom of your choice.
Click to expand...
Click to collapse
given a choice, i'd like to do what's bolded in red - but that's what i thought i was doing by flashing the cwm file i downloaded from the cwm website - but after the flash attempt it wouldn't boot into cwm, it would just boot into (i'm assuming") the stock rom i restored, which was a mess. i also unchecked auto-boot to see if that helped - but when i manually booted it didn't boot into cwm, it booted into the stock recovery, with the animated android.
i'll try downloading cwm from the sources you provided, and see if that does the trick. btw, why do you think i was able to flash the cm11 rom with (seemingly) perfect success, but wasn't able to restore either one of the full system (android) backups i made after i rooted my phone?
anyway Skipjack, thanks a ton for your assistance and i'll report back after i give your sources a try. fwiw, it sure is a great charge when a newbie like me sees a custom rom load for the first time, displaying a new ui as it boots, fun stuff.
Just download the ready yo flash tar files. Cwm has them. Twrp has them.
success Skipjack thanks to your generous time and assistance!
i ended up downloading the latest odin zip i could find and philz_touch_6.08.9-jfltetmo.tar.md5... my first try didn't take, with auto-reboot checked, my phone simply rebooted into the same problematic rom i had restored. i then tried it with auto-boot unchecked and manually booted when odin reported pass/success, and it worked. what struck me as odd was how long it took to flash, to report pass/success, around 3-5 minutes if i had to guess, a big difference compared to when i first used odin to root my phone with the["SGH-M919] CF-Auto-Root *.tar.md5 file - i'm guessing that's why it didn't work with auto-boot checked, just took too long?
anyway once i booted into philz_touch recovery i executed the wipe data/factory reset > clean to install a new rom command and then flashed the cm11 m7 (snapshot) rom, which i had flashed once before, right before i attempted to restore the stock rom it had replaced. and as was the case the first time around, it installed without a hitch and is running smooth and fast.
however now when i boot the phone, as soon as the cyanogen logo appears, very tiny text appears in the upper left hand corner which reads (i had to use a magnifying glass!) - it doesn't seem to effect the performance of he device but i'd like to get to the bottom of it, i've already searched and it appears to be a rather common issue.
kernel is not seandroid enforcing
set warranty bit: kernel
btw, i forgot to mention, when i purchased my sgh-m99 it already had 4.3 installed - when i flashed my first rom (cm11 m7) it included kitkat 4.4.2... could this be what caused my problems? did trying to go back to (restore) a 4.3 rom after flashing a 4.4.2 rom screw things up? can this even be done successfully?
and finally, at the risk of bugging the heck out of you, what roms do you prefer for your s4, assuming you have an s4? do you like aosp roms or touchwiz? does one type have a better reputation of being more stable? the primary reason i wanted to rot my phone was to get rid of a bunch of t-mobile / samsung bloatware, which i thought i could do by installing a lean custom rom. any suggestions, which are your favorites? thanks again Skipkack.
ouhned after
re the two lines of text i now get in the upper left hand corner of the screen whenever i boot, the kernel message:
kernel is not seandroid enforcing
set warranty bit: kernel
well after a lot of searching and reading, including coming across dozens of "fixes" and "solutions" that didn't seem to work for many folks, these two responses seemed to make some sense, what do you think?
eclpsues said:
I'm not an expert in Android OS but I think this is not an error. It is more of a notification that the STOCK KERNEL has been change to a CUSTOM one.
Click to expand...
Click to collapse
Joku1981 said:
You are right.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2594483
aeneas1 said:
re the two lines of text i now get in the upper left hand corner of the screen whenever i boot, the kernel message:
kernel is not seandroid enforcing
set warranty bit: kernel
well after a lot of searching and reading, including coming across dozens of "fixes" and "solutions" that didn't seem to work for many folks, these two responses seemed to make some sense, what do you think?
http://forum.xda-developers.com/showthread.php?t=2594483
Click to expand...
Click to collapse
The tiny text on the boot screen is basically telling you that Knox has been tripped. You are right. It does not affect the performance of the phone.
Skipjacks said:
The tiny text on the boot screen is basically telling you that Knox has been tripped. You are right. It does not affect the performance of the phone.
Click to expand...
Click to collapse
thanks skipjack... btw i'm really liking the cm11 m7 rom but, via the learning curve process, i've discovered it does not support wifi calling, something that apparently all aosp rom lack, guess i'll have to go with a touchwiz rom even tho the selection seems to be few and far between. also, is it possible to revert back to 4.3 once 4.4.2 has been flashed? seems like there's a lot of mixed opinions on this, altho in terms of those opinions it's hard for me tell who the pros are that should believed, and who the other guys are that really don't know. thanks again.
aeneas1 said:
thanks skipjack... btw i'm really liking the cm11 m7 rom but, via the learning curve process, i've discovered it does not support wifi calling, something that apparently all aosp rom lack, guess i'll have to go with a touchwiz rom even tho the selection seems to be few and far between. also, is it possible to revert back to 4.3 once 4.4.2 has been flashed? seems like there's a lot of mixed opinions on this, altho in terms of those opinions it's hard for me tell who the pros are that should believed, and who the other guys are that really don't know. thanks again.
Click to expand...
Click to collapse
Once you are rooted you can flash any custom ROM 4.3, 4.4, 4.2, etc. and then go back to stock 4.3. And only TW ROMs allow wifi calling
Sent from my SGH-M919 using XDA Premium 4 mobile app
Kriptik210 said:
Once you are rooted you can flash any custom ROM 4.3, 4.4, 4.2, etc. and then go back to stock 4.3. And only TW ROMs allow wifi calling.
Click to expand...
Click to collapse
very interesting... i guess i misunderstood the posts i read on the subject, maybe they were discussing whether or not you could revert to 4.3 from 4.4.2 on non-rooted phones, which i'm guessing isn't possible. anyway, as i mentioned previously, i fist rooted my 4.3 phone, did a full system backup (using online nandroid), flashed a 4.4.2 rom which worked perfectly, then tried to restore my 4.3 backup only to encounter a bunch of problems, thought going from 4.4.2 back to 4.3 may have caused the problems but i guess not?
so if i'm using a 4.4.2 custom rom and want to restore a 4.3 backup i should be able to boot into recovery and restore from there? or would i need to do a 4.3 flash first, before restoring a 4.3 backup?
aeneas1 said:
very interesting... i guess i misunderstood the posts i read on the subject, maybe they were discussing whether or not you could revert to 4.3 from 4.4.2 on non-rooted phones, which i'm guessing isn't possible. anyway, as i mentioned previously, i fist rooted my 4.3 phone, did a full system backup (using online nandroid), flashed a 4.4.2 rom which worked perfectly, then tried to restore my 4.3 backup only to encounter a bunch of problems, thought going from 4.4.2 back to 4.3 may have caused the problems but i guess not?
Click to expand...
Click to collapse
Did you wipe before you restored? And do not misunderstand this, you cannot downgrade firmwares once you go 4.3 and up, but you can downgrade the system, which is what you did with your backup
serio22 said:
Did you wipe before you restored? And do not misunderstand this, you cannot downgrade firmwares once you go 4.3 and up, but you can downgrade the system, which is what you did with your backup
Click to expand...
Click to collapse
thanks very much for the clarification, i was under the impression that firmware and system were somewhat synonymous in this context, i.e. if you upgraded firmware you were in effect upgrading the system, but i see that's not the case, again thanks. and yes i did do a full wipe before trying to restore the backup, was i not supposed to?
aeneas1 said:
thanks very much for the clarification, i was under the impression that firmware and system were somewhat synonymous in this context, i.e. if you upgraded firmware you were in effect upgrading the system, but i see that's not the case, again thanks. and yes i did do a full wipe before trying to restore the backup, was i not supposed to?
Click to expand...
Click to collapse
Updating firmware does update the system. Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware. Firmware consists of bootloader, recovery, modem, and system, what you cannot downgrade is the bootloader, the flash will fail every time because it will try to downgrade it. And you should not experience any issues restoring your back up. What were this problems?
btw serio22, do you have a favorite tw rom?
Yea serio22, what is your favorite TW ROM?
Sent from my SGH-M919 using XDA Premium 4 mobile app
serio22 said:
Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware.
Click to expand...
Click to collapse
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
btw, fwiw, - now that i'm up and running thanks to skipjacks help, i decided to try restoring my 4.3 backup again. when i tried this in the past it would restore to the same state as it was before but it was virtually unusable because of severe lags and multiple app not working popups that made navigating almost impossible. well now when i try to restore it fails and i get the following message:
checking md summs...
md5 mismatch
serio22 said:
Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware.
Click to expand...
Click to collapse
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
btw, fwiw, - now that i'm up and running thanks to skipjacks help, i decided to try restoring my 4.3 backup again. as i mentioned, when i tried this in the past it would restore to the same state as it was before but it was virtually unusable because of severe lags and multiple "app not working" popups that made navigating almost impossible. but now when i try to restore the 4.3 backup it fails and i get the following message:
checking md summs...
md5 mismatch
update:
well it looks like the *.md5 file was pointing to my internal drive rather than external which is where i had moved the 4.3 backup (and apparently the *.md5 file didn't update or account for the move), anyway i copied the backup to my internal drive and, viola, no more md5 mismatch errors. more importantly, it restored the 4.3 backup perfectly, in the exact same state as before, without all of lagging and pop up issues i was having before, so i'm one happy camper! not sure what i did the first time around, but all is good now, for he time being, sure wish i knew what i mucked up to cause the problems in the first place, i really have no idea, other than being a newbie at this. also, fwiw, the tiny text in the upper left hand corner that appears during boot (kernal message) no longer appears now that i have restored the 4.3 system backup... fwiw2, i'm liking the philz_touch_recovery but it sure has taken some getting used to, the commands are so close together and the thing is so sensitive, very easy to accidentally select the wrong option, and some of the wrong options aren't too friendly if it wasn't what you had intended to select.
aeneas1 said:
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
Click to expand...
Click to collapse
Read my previous post more closely below. Good to see you up and running though! And no I don't have a favorite tw Rom
serio22 said:
Updating firmware does update the system. Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware. Firmware consists of bootloader, recovery, modem, and system, what you cannot downgrade is the bootloader, the flash will fail every time because it will try to downgrade it.
Click to expand...
Click to collapse
Hi XDA friends
I have a Nexus 5x on build MDB08I. It's rooted and encrypted with the encryption-compatible TWRP.
I really want to update to 6.0.1 but I don't want to have any data loss (i made a Nandroid backup recently but it's just a pain in the ass to set up a phone from scratch). Is this safe slash possible currently? I don't care about losing root, I just want to get the update, and keep all data and TWRP intact.
If so, can anyone help me out with what files I need and where to get them? I've got android SDK, familiar with fastboot, etc. but I just don't know what to flash and not flash. I do know that I can't just flash the OTA zips, tried that a few times
From what I've found looking around, it seems possible if I extract the files from the factory image of MMB29K and do the following:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
wipe cache/dalvic in TWRP
reboot
flash SuperSu in recovery
Click to expand...
Click to collapse
And... that's it? Do I have to flash radio, bootloader, recovery, etc? Will TWRP work with MMB29K? If it fails, I can revert to my nandroid backup. BUT I want to confirm that the above plan does not risk a brick.
Thanks!!
Read this thread http://forum.xda-developers.com/showpost.php?p=64253043&postcount=289
That specific post has the list of steps you should do to upgrade and regain root without losing your data. You can find the modified MMB29K boot.img file in another post on this forum.
solara1973 said:
Read this thread http://forum.xda-developers.com/showpost.php?p=64253043&postcount=289
That specific post has the list of steps you should do to upgrade and regain root without losing your data. You can find the modified MMB29K boot.img file in another post on this forum.
Click to expand...
Click to collapse
I followed that list but my phone has been booting for 20+ minutes. I'll restore from nandroid, but any idea what I did wrong? Should i fastboot flash iteratively from I to L to M and then to K instead of directly from I to K? do i have to boot into the OS after each build flash?
thanks!
edit: hah, wow. didn't even have to nandroid, just re-flashed all the I img's and all is back to normal. next i'll try the L, M, K sequence and report back unless you have any other ideas what i did wrong
You do not need to flash each version if you are flashing the images from the full firmware you download from Google. When you say it takes 20 mins where is it hanging at? It took a while for my 54 apps to get updated after flashing and clearing cache before booting into the system. You should not boot into system until you've flashed everything. You do reboot to bootloader after you flash the new bootloader.
Make sure you flash MODIFIED boot image for MMB29K if you were rooted with /system SU on L, otherwise you'll get boot loop. Also flash new radio too if you want Tmo band 12.
mickey4mice said:
Make sure you flash MODIFIED boot image for MMB29K if you were rooted with /system SU on L, otherwise you'll get boot loop. Also flash new radio too if you want Tmo band 12.
Click to expand...
Click to collapse
oops, that's it -- i had flashed the boot.img from the google image. found another XDA thread w/ modified MMB29K boot.img so trying that
@Solara i left it at the new boot animation for like an hour, the one with the 4 cute circles acting all busy.
also what does flashing cache and then wiping it do? why flash if if your'e gonna wipe it right after? new file format?
thanks so much guys!
edit: all set! did the same thing with the modified boot.img this time. also discovered i had to re-flash TWRP. still wondering what the deal with the cache/dalvik is but i flashed and wiped and everything seems great.
I didn't mean flash the cache image then clear it. I mean flash all the specified images then clear the cache. Just look at that original link I posted. Pretty clear and easy steps.
solara1973 said:
I didn't mean flash the cache image then clear it. I mean flash all the specified images then clear the cache. Just look at that original link I posted. Pretty clear and easy steps.
Click to expand...
Click to collapse
deffo, very simple and it's awesome that this **** is even possible due to all the work devs and volunteers do i've seen elsewhere people saying they flashed cache.img and then wiped it so it sounds like they were flashing it unnecessarily
This is confusing the heck out of me. So I realize there's 2 partitions and why they're there. So the B partition is just a fresh blank copy of whatever image you're on? I see posts about flashing to a and b, but when I look in a stock image folder they aren't labeled a and b. My pixel is in the stock October ROM. I flashed TWRP alpha 2 as alpha 1 and rc1 just showed the TWRP splash screen and kept flickering. I backed up my stock os then wiped and flashed pure nexus. Wouldn't flash, some Android binary update error (I've heard my boot.img was the wrong version possibly?). Said okay, just restore my backup. Did that and looked like everything went fine, rebooted and it rebooted right back to TWRP, wouldn't boot to os. Eventually just flashed the stock October image. Am I missing something? Do I need to be on a newer Android version for the rc1 TWRP to work? Any help is appreciated, thank you.
To get out of the bootloop just dl latest factory Image from Google and flash bootimage to slot a and b.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
So my backup restore most likely went fine, I just missed this step?
danielson2047 said:
So my backup restore most likely went fine, I just missed this step?
Click to expand...
Click to collapse
did you first boot to twrp and then flashed twrp zip from twrp?
also, any particular reason for being still at October software?
I wasnt sure my unlock would stick if I flashed new image (Verizon edition).
danielson2047 said:
I wasnt sure my unlock would stick if I flashed new image (Verizon edition).
Click to expand...
Click to collapse
Don't have Verizon edition, but pretty sure it wouldn't lock it.
danielson2047 said:
I wasnt sure my unlock would stick if I flashed new image (Verizon edition).
Click to expand...
Click to collapse
It won't.
I don't see it ever doing that. One, I am not sure it is even possible. And 2 it would trigger a full data wipe. Even VZ isn't crazy enough to wipe peoples data. The FCC fine would be massive not to mention tje probable class action lawsuits.
So can i keep my stock rom as is and use twrp to flash to the "b' side? I suppose as soon as i'd update the stock side it would just override the b side huh.
TonikJDK said:
It won't.
I don't see it ever doing that. One, I am not sure it is even possible. And 2 it would trigger a full data wipe. Even VZ isn't crazy enough to wipe peoples data. The FCC fine would be massive not to mention tje probable class action lawsuits.
Click to expand...
Click to collapse
Good thought. I was thinking in terms of "poor me my phones locked". Never thought about it from the data side.
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.