Related
I'm very frustrated with my player, I rooted it last year and flashed Pacrom venturi 2013-11-05 JB and sultan kernel, cwm 6.0.4.4, it wasn't easy it took me like 6 hours with lots of problems but at the end it was done. Now I tried to update it to KK and I've been trying for days. The first rom I tried was Pacrom venturi 20140407 with cwm 6.0.4.4 and I think sultan kernel and I had no problems except the wifi didn't work so I didn't backup and tried to flash it again but it didn't work because status 0 and status 7 and I tried several times to no vail so I downloaded one by one all the nightlys from April some of March, some from January, the one that used to work in from november, so I tried 4.4 - 4.3- 4.2.2 - 4.2 -4.1, pacrom, slimkat, cm, beanstalk, sultan kernel, Mercurius v5, Mercurius reborn, CM kernel, KKernel, CWM 6.0.4.4, 6.0.4.3, 5.0.2.7 and non worked. I've tried flashing it like 200 times of those, maybe like 5 times was successful but as soon I flash the kernel and then restart the screen its black nothing appears, I tried the build from july and the keyboard keep on crashing, so this is some of the thing that I've experienced
Most builds won't install because errors 0 and 7
"some symlinks failed status 7"
assert failed status 7
error status 4 installation aborted
E: Error in /sdcard/"name of rom".zip (status 0)
there're more that I didn't keep track of
I re-downloaded the roms twice to make sure it wasn't because a corrupt zip
If I successfully flash a rom, once I flash the kernel and fails, I can't re-flash the same built because errors start appearing
sometimes I get different versions of CWM depending of the rom.
presently I flashed CM 10.2 20131105 venturi, android 4.3.1 and gapps from july 2013 built-in kernel version 3.0.1.101-G70UEKI8 but the capacitive buttons don't work so I tried these kernels: Mercurius_kernel_usa_v5fixed, KKernel_R2.1_usa, Sultan-kernel-Venturi-r5-USA, Mercurius_Reborn_RC1_usa, pac-cm-USKernel-Mar-03, cm-10.2-USA-Kernel-REV5 but once I restart,the screen is black so I have to do a restore to just before the flashing of the kernel but can't use it like this.
Any sugestion? Any other kernels? I'm about to give up.
I'm on stock and love my YP-G70, everything just works and I can customize it as I like. Except for the times I load too many widgets I have no problems. I see NO reason to change to ROMs with less functionallity and lots of problems. 2.3 is THE most stable and most used version of Android. If it ain't broke don't fix it. Mine "looks" like the S4 and works like it too, why would I change? KISS
tapia818 said:
I'm very frustrated with my player, I rooted it last year and flashed Pacrom venturi 2013-11-05 JB and sultan kernel, cwm 6.0.4.4, it wasn't easy it took me like 6 hours with lots of problems but at the end it was done. Now I tried to update it to KK and I've been trying for days. The first rom I tried was Pacrom venturi 20140407 with cwm 6.0.4.4 and I think sultan kernel and I had no problems except the wifi didn't work so I didn't backup and tried to flash it again but it didn't work because status 0 and status 7 and I tried several times to no vail so I downloaded one by one all the nightlys from April some of March, some from January, the one that used to work in from november, so I tried 4.4 - 4.3- 4.2.2 - 4.2 -4.1, pacrom, slimkat, cm, beanstalk, sultan kernel, Mercurius v5, Mercurius reborn, CM kernel, KKernel, CWM 6.0.4.4, 6.0.4.3, 5.0.2.7 and non worked. I've tried flashing it like 200 times of those, maybe like 5 times was successful but as soon I flash the kernel and then restart the screen its black nothing appears, I tried the build from july and the keyboard keep on crashing, so this is some of the thing that I've experienced
Most builds won't install because errors 0 and 7
"some symlinks failed status 7"
assert failed status 7
error status 4 installation aborted
E: Error in /sdcard/"name of rom".zip (status 0)
there're more that I didn't keep track of
I re-downloaded the roms twice to make sure it wasn't because a corrupt zip
If I successfully flash a rom, once I flash the kernel and fails, I can't re-flash the same built because errors start appearing
sometimes I get different versions of CWM depending of the rom.
presently I flashed CM 10.2 20131105 venturi, android 4.3.1 and gapps from july 2013 built-in kernel version 3.0.1.101-G70UEKI8 but the capacitive buttons don't work so I tried these kernels: Mercurius_kernel_usa_v5fixed, KKernel_R2.1_usa, Sultan-kernel-Venturi-r5-USA, Mercurius_Reborn_RC1_usa, pac-cm-USKernel-Mar-03, cm-10.2-USA-Kernel-REV5 but once I restart,the screen is black so I have to do a restore to just before the flashing of the kernel but can't use it like this.
Any sugestion? Any other kernels? I'm about to give up.
Click to expand...
Click to collapse
check in the zip file if you have 4/3 files (file_contents boot animation meta-inf system
if yes go check if the 4 files are in the directory / home / beggining folder in the zip if no then extract it then select all 4 files and then send to zip
captpete1 said:
I'm on stock and love my YP-G70, everything just works and I can customize it as I like. Except for the times I load too many widgets I have no problems. I see NO reason to change to ROMs with less functionallity and lots of problems. 2.3 is THE most stable and most used version of Android. If it ain't broke don't fix it. Mine "looks" like the S4 and works like it too, why would I change? KISS
Click to expand...
Click to collapse
I agree, GB is a very stable version, but I own a phone with JB installed and sometimes I don't want waste my phone battery so I use the galaxy but when it had GB, it was a downgrade for me, it was slow and could not install chrome which it's a must for me and with other roms looks and runs great ( when it used to).
It has everithing
sabirchowdhury said:
check in the zip file if you have 4/3 files (file_contents boot animation meta-inf system
if yes go check if the 4 files are in the directory / home / beggining folder in the zip if no then extract it then select all 4 files and then send to zip
Click to expand...
Click to collapse
I tried to re-zip one build and when I tried to flashed it status 4 came up.
Right now I was able to flash pac_venturi-nightly-20140410.zip with gapps 2014-01-05 and its working but I think that I'm using the wrong kernel for the US version because when I restart my YP-G70 stays in the Pacrom logo or galaxy S Cyanogen (mod) like frozen.
Do anyone know of a rom and kernel for the us version of KK? or the kernel for this build that I flashed and seems working because I backed up and can restore it to before flashing the kernel thank you.
tapia818 said:
I tried to re-zip one build and when I tried to flashed it status 4 came up.
Right now I was able to flash pac_venturi-nightly-20140410.zip with gapps 2014-01-05 and its working but I think that I'm using the wrong kernel for the US version because when I restart my YP-G70 stays in the Pacrom logo or galaxy S Cyanogen (mod) like frozen.
Do anyone know of a rom and kernel for the us version of KK? or the kernel for this build that I flashed and seems working because I backed up and can restore it to before flashing the kernel thank you.
Click to expand...
Click to collapse
have you tried
http://forum.xda-developers.com/showthread.php?t=2568478
My partner's S III recently developed a problem using the standard Samsung 4.3 OS, it kept halting in the the middle of an application and later started continuously rebooting. As the phone was as far as I was aware, out of warranty and someone suggested there could be a s/w issue, I decided to root the phone and install a custom 4.4.2 ROM (I initially went for the one of the cyanogenmod 4.4.2 ROMs), to see whether that would resolve the problem. Initially, the ROMs I tried all generated error messages and failed to install,until I tried the Revolutioniary S5 V2 ROM, which installed perfectly.
However, it states that iti is a 4.3, rather than 4.4.2 ROM. I ran the ROM for 5 days without any major issues, so decided to try the V3 ROM, as ir was stated that this was 4.4.2 in a number of articles.. Again the ROM installed really quickly and without a hitch. However, again the ROM said it was 4.3, and as soon as I tried to install applications (well it was the third install, Skype if I remember), and the phone turned itself off. Then it started continuously rebooting, which is what was happening before the V2 ROM was installed. managewd to stop this by removing and then putting back the battery, and managed to get the V2 ROM installed again. Ther are three questions:
1) Does anyone have any idea what the initial problem might have been?
2) Why did the V3 ROM actually cause the problem to reoccur?
3) Is there a genuine 4.4.2 release of the Revolutionary S5 ROM (which I am genuinely impressed by and happy with), and will it work with my phone? (specific model i9300)?
[email protected] said:
My partner's S III recently developed a problem using the standard Samsung 4.3 OS, it kept halting in the the middle of an application and later started continuously rebooting. As the phone was as far as I was aware, out of warranty and someone suggested there could be a s/w issue, I decided to root the phone and install a custom 4.4.2 ROM (I initially went for the one of the cyanogenmod 4.4.2 ROMs), to see whether that would resolve the problem. Initially, the ROMs I tried all generated error messages and failed to install,until I tried the Revolutioniary S5 V2 ROM, which installed perfectly.
However, it states that iti is a 4.3, rather than 4.4.2 ROM. I ran the ROM for 5 days without any major issues, so decided to try the V3 ROM, as ir was stated that this was 4.4.2 in a number of articles.. Again the ROM installed really quickly and without a hitch. However, again the ROM said it was 4.3, and as soon as I tried to install applications (well it was the third install, Skype if I remember), and the phone turned itself off. Then it started continuously rebooting, which is what was happening before the V2 ROM was installed. managewd to stop this by removing and then putting back the battery, and managed to get the V2 ROM installed again. Ther are three questions:
1) Does anyone have any idea what the initial problem might have been?
2) Why did the V3 ROM actually cause the problem to reoccur?
3) Is there a genuine 4.4.2 release of the Revolutionary S5 ROM (which I am genuinely impressed by and happy with), and will it work with my phone? (specific model i9300)?
Click to expand...
Click to collapse
1) Not doing a full wipe/ formating system cache data etc or not using the latest recovery or combination of both
2) Not doing a full wipe/ formating system cache data etc or not using the latest recovery or combination of both
3) No
Also I find if switching between 4.3 roms and 4.4 roms (which I do alot) it is good idea to backup internal sd card and to format it (not all the time just if phone becomes really slow or has random reboots)
Here's a Stockish ROM for your N915P. This ROM has Knox, Sprint ItsOn, and secure storage removed. Nothing else was done to this ROM. I'm new to the Note Edge so I may upload patches to remove any other traces of Knox or ItsOn or optimizations I happen to find while making my own ROM.
Prereq: OG1 Baseband. Download it below.
Modified stock kernel (BeastMode Stock): Kernel modified to allow root by disabling "Root Restriction in defconfig"
Download
MD5: 75bd507e3b4296a128f1c0c48fd2359c
Version 1.1: Enabled many TCP Congestion options via defconfig. Added init.d ability via ramdisk.
Odex:
Download
MD5: 59d544ef6a4bc12d969f4efd9577d36d
DeOdex DEBLOATED:
Download
MD5: 00b5246b9c2074e7ff04f6af2bad1ec2
OG1 Baseband:
Download
MD5: 3bc88209d60117fb573e0f5a2e50f4e9
Patches and fixes:
None yet.
[size=+3]DeOdex note:[/size]
The first boot time for this DeOdex ROM is very long. Approximately 5-8 minutes. Your phone will get hot as the splash screen remains on the yellow Sprint boot animation. I recommend keeping your phone in a cool environment while this is happening. The heat, if not properly checked, can make boot times even longer as the system throttles speed in order to deal with the heat. This doesn't happen on the Odex version.
[size=+3]Install instructions:[/size]
-Are you currently on the OC8 bootloader and would like to stay on it?
--Simply flash the baseband with Odin, and the ROM.
-Are you on the update from OTA or flashed the OG1 TAR?
--Flash kernel only.
-Are you one of the unlucky ones to take the OTA and hose your system trying to root and are now on another ROM?
--Flash ROM only.
-Are you on any build after OC8 but not the current OG1?
--Flash the baseband and ROM. Bootloader is optional and not available in this thread as of yet.
Wiping is only necessary if you are coming from a different base, such as AOSP/CM. If you are coming from a touchwiz ROM, wiping isn't needed, but won't hurt.
Changelog:
9/5/15: Initial Release.
Kernel source code: Download
Thanks, will flash tomorrow.
Thank you so much freeza!! Patiently waiting for the deodexed version and for the baseband.
Added modified stock kernel v1.1 and baseband.
Freeza if I'm on 5.0.1 still just flashing the baseband may give me better service ? Technically...
Downloading now still waiting on the deodex will play with the stock to see how it is thanks
Ok, flashed rom, kernel, and modem. Took a while to boot but all is running well at the moment. Thanks for supporting our device!!
DeOdex uploading....
What What!!! By far the best developer on a Samsung!! Thank you so much for your hard work brother!! Real Talk, i still have your rom on my Note 3! It runs flawlessly!! XD
Get your DeOdex on, guys! ;D
Thanks so much for this!!! I love the separate edge screen and have no reason to "upgrade" to the Note 5
Thank you freeza NICE WORK WITH THE KERNEL
When I saw you had been requested to come help this phone achieve root I knew great things were going to come to those who waited. I've had other devices where you were there to help gain root and again you came through. I purposely didn't take the OG1 update because I knew in time this device wasn't going to be ignored. IMO it is the best NOTE device out there and it will be mine until they make a NOTE EDGE 2 (With SD card and removable battery). Thank you for the quick response and the hard work you do to make this happen.
Cant get either one of them to boot. Both the odex and the deodex wont boot, they both flash fine and then after the phone reboots it stays on the yellow sprint screen Maybe for up to a minute then reboots and it cycles that way. Never boots. I've tried not wiping/Factory restarting as well as wiping/Factory resetting. Have also tried formatting through TWRP to no avail. Have also tried flashing the kernel and wiping caches after flashing but Nothing is working. Have also flashed the baseband.
Im currently on OF6 if that should matter.
Edit: md5 Sums have also match up. Have downloaded both from my phone and a pc to no avail.
Edit 2: tried both TWRP 2.8.6.0 and 2.8.7.0. Also tried clockworkmod recovery and that didn't work either.
I had success but it took some time. I downloaded the deodexed debloated rom, the kernel, and the baseband. I had a method to how I wanted to do this and here is how i got there.
I was running OC8 rom rooted.
1. I odened the baseband tar file and rebooted. But unfortunately it bootlooped on the initial splash screen (note edge) so
2. I ran TWRP recovery and installed the kernel file. Rebooted phone and it ran fine. I looked at the settings about phone and saw that the baseband and the rom all said OG1 but i had not installed the rom yet. So i figure it was a trick to get the baseband to install. So
3. I went back into recovery. Wiped dalvik cache and regular cache and installed the new rom. It installed fine and i waited the length of time for the initial boot up. But this time as it was "Android is starting" it rebooted and got stuck on the sprint splash screen and kept randomally vibrating. Having the ability to remove the battery
4. Rebooted back into recovery, wiped everything including internal storage, and reinstalled the deodexed rom. It installed fine and went to the initial startup screen where it tries to initialize and it rebooted one time, back to the initialize screen but continued without a hitch.
I currently am running OG1 5.1.1. With root.
At times during setting up the phone it would randomally vibrate for no reason...short bursts...but it hasn't yet again rebooted, restarted, or crashed. It is faster from what i see. Probably because there are almost no google apps installed. I've had to install chrome, youtube, and maps. But all seems fine. My signal and speeds are the same so the baseband didn't do much to change that. But so far so good.
---------- Post added at 11:30 AM ---------- Previous post was at 11:27 AM ----------
I did try to install over my odexed OC8 with this new rom but because there is so much different about the files that are installed IMO formatting the phone was the only way to get this to work.
---------- Post added at 12:16 PM ---------- Previous post was at 11:30 AM ----------
One final thing just in case it isn't known: when you wipe everything in TWRP, excluding external storage, you have to restart the recovery before trying to install a rom. It will say you have no OS installed, but you are restarting the recovery not booting a rom, so that's fine, but you do lose root status when wiping. So the next screen gives you the ability to gain root again, but you have to restart TWRP to do that. In the past i tried to figure out why installing after wiping didn't work, and 99% of the time it was because of that. I also don't like installing new roms over older roms (even if they are the same base (touchwiz to touchwiz)) because i feel I would spend more time troubleshooting why something isn't working instead of just starting over. I find less hassle doing it this way.
I odin baseband .tar file, than reboot it to recovery, and flash kernal and odex room at the same time, saw some red messages when kernel was flashing, than odex rom was next but it was successful when it was done. (I did not know if kernel falsh ok so i reflash kernel again) reboot to system and after the android system updated all its ok. No problems so far.
Oh and i inclided the supersu at the same time i flash kernel, odex rom and supersu.
1. Odin baseband tar file.
2. Flash kernel, odex rom and supersu.
3. Re-flash kernel.
4. Reboot to system and profit.
(Maybe i did un necessary steps, but its working. )
Was running great but have been experiencing Google account and store issues. Tried odex and deodex versions with similar results. Anyone else having issues?
Johnny Halo III said:
Was running great but have been experiencing Google account and store issues. Tried odex and deodex versions with similar results. Anyone else having issues?
Click to expand...
Click to collapse
Just starting to have random freezing. And not able to select my apps froms the edge screen, i can only scroll through it. Will remove all the app shorcuts and re-add tham again.
**update 1.
I removed all shorcuts from the edge screen and added them back, all work but some i have to select them a few times before they open.
Maybe i have to reflash, reset, clean and wipe.
**update 2.
Clean install of odex rom, and kernal 1.1.
No more lagg but the edge screen does not work properly. Not able to select and open some of the favorite app shorcuts.
**update 3.
Factory reset, cleaned and wype, odin sprint lollipop update (uf something), downloaded OG1 update. Installed all apps from scratch. And the edge screen does not work. I can scroll, side to side, up and down, but when i select an app it does not open it.
** update (last one)
Foud the code to test the phone hardware.
*#0*# on dial screen. Tested all and it came out good. But i notice that some how the edge screen its not as whide as it used to be ( like its more to the right of the phone) so where i use to touch to select an app its now more to the right emd of the edge, thats why i was able to scroll but not select the app.
Its all good now. Now second round of flashing.
Will give it another try at the room.
Thanks Freeza and sorry about the problems i had and hopefully did not cause anyone from not trying this great work pr yours.
I left all the problems i had so tje next person trying this room does not get discureged from trying. But allways fallow direction.
:thumbup:
** last update
After setting and resetting, flashing and un-flashing, rooting and un-rooting. I can finally wrote that all is good. Running latest lollipop 5.1.1 and freeza's new 1.1 kernel, I can reprt that all is smooth as butter.
Thanks for the hard work.
Thank you so much for your hard work Freeza! So glad I'm finally running 5.1.1 on this beast :]
The ROM is working pretty well, but I have noticed that every now and then, the phone will be rather laggy. Turning the screen off and on again seems to fix the issue, making me think that the processor is being throttled while the screen is off (good) but isn't being sped back up when the screen is turned on..sometimes.
It's not a huge deal, but I was wondering if anyone was experiencing the same thing.
No issues here.
Starting on OG1 had to flash bootloader, kernel, deodex rom and supersu to make it stick. Two days now and battery, signal and speed seem improved.
Thanks freeza!
I have a rooted HDX 7" 3rd gen that I have been running CM 11 on using Safestrap, and I would like to try and get a different rom running on it. I did a factory reset back to FireOS 4.5.2. I'd really love to get CM 13 running, but I'm not sure how to do it or if it's even an option at this point. I am trying to make sense of my different options but I'm pretty confused at this point. Am I stuck with CM 11 for now or is this even possible? If not is CM 12 or Nexus a possibility? Thanks!
You can NOT use CM13 and CM12 with Safestrap v4! Both require an unlocked bootloader, you can NOT downgrade below 3.2.8 due to rollback protection by Amazon (attempt would brick the device), thus you can't unlock the bootloader.
You can use CM11 or Nexus for Safestrap v4 only.
matt_2_27 said:
I have a rooted HDX 7" 3rd gen that I have been running CM 11 on using Safestrap, and I would like to try and get a different rom running on it. I did a factory reset back to FireOS 4.5.2. I'd really love to get CM 13 running, but I'm not sure how to do it or if it's even an option at this point. I am trying to make sense of my different options but I'm pretty confused at this point. Am I stuck with CM 11 for now or is this even possible? If not is CM 12 or Nexus a possibility? Thanks!
Click to expand...
Click to collapse
Cl4ncy said:
You can NOT use CM13 and CM12 with Safestrap v4! Both require an unlocked bootloader, you can NOT downgrade below 3.2.8 due to rollback protection by Amazon (attempt would brick the device), thus you can't unlock the bootloader.
You can use CM11 or Nexus for Safestrap v4 only.
Click to expand...
Click to collapse
Pretty amazing your device survived the factory reset. In most cases that yields an instant brick when Safestrap v4 recovery is installed/active. Did you have CM 11 installed in the stock slot or a secondary slot (eg: slot 1)?
Davey126 said:
Pretty amazing your device survived the factory reset. In most cases that yields an instant brick when Safestrap v4 recovery is installed/active. Did you have CM 11 installed in the stock slot or a secondary slot (eg: slot 1)?
Click to expand...
Click to collapse
I had the stock rom in the stock slot and had CM 11 in a secondary
matt_2_27 said:
I had the stock rom in the stock slot and had CM 11 in a secondary
Click to expand...
Click to collapse
That's not the recommended configuration and likely contributed to a sub-optimal experience. Issues:
- only 2 of the 4 processor cores can be used (poor performance under load)
- those two core run at 100% all the time (poor battery life)
- device never deep sleeps (variety of issues including thermal)
- wifi radio is slow to engage during power transitions
- limited user space for apps/data
- instant brick if a slot backup is restored to the stock slot or vice versa
Custom ROMs should always be installed in the stock slot (overwriting FireOS) with Safestrap v4 which is exclusive to HDX 3rd gen devices. A safestrap compatible version of FireOS can be flashed if needed allowing the device to return to stock. Secondary slots should not be created/used.
Davey126 said:
That's not the recommended configuration and likely contributed to a sub-optimal experience. Issues:
- only 2 of the 4 processor cores can be used (poor performance under load)
- those two core run at 100% all the time (poor battery life)
- device never deep sleeps (variety of issues including thermal)
- wifi radio is slow to engage during power transitions
- limited user space for apps/data
- instant brick if a slot backup is restored to the stock slot or vice versa
Custom ROMs should always be installed in the stock slot (overwriting FireOS) with Safestrap v4 which is exclusive to HDX 3rd gen devices. A safestrap compatible version of FireOS can be flashed if needed allowing the device to return to stock. Secondary slots should not be created/used.
Click to expand...
Click to collapse
Good to know! There wasn't anything I saw during my research about this when I first set it up with CM 11.
Also, does anyone know of a way to get Wii Remotes to work with either CM 11 or Nexus. I know they don't seem to work with Android 4.2 and higher and since both CM 11 and Nexus are running higher versions am I out of luck?
I have now worked with 4 Thor devices - two I've owned for quite a while and 2 I've purchased used as media streamers for friends. Every one of them reboots itself with screen autorotation on when using either the kk-fire-nexus-rom or the CM-11 for Safestrap ROM. It doesn't always happen immediately, but always within a few minutes of use. None of the LP, MM, or N-based custom ROMs I've tried have ever done this. I'd ideally like to load one of those KK-based ROMs for bluetooth support.
I've prepared each tablet the same way, every time (starting point was always FireOS 4.5.5.1):
1. Root the device and then copy the custom ROM to it
2. Grab the serial/manfid
3. Flash TWRP (either 3.0.2.0 or 3.0.0.1) and the vulnerable bootloader with the dd command
4. Successfully unlock the bootloader
5. From TWRP, wipe everything except internal storage, then install the ROM
6. Wipe cache/dalvik, reboot
This is driving me nuts, since I see users so satisfied with these KK ROMs and little mention of this as an issue. Can anyone see what I'm missing? Thanks.
Bawdy George said:
I have now worked with 4 Thor devices - two I've owned for quite a while and 2 I've purchased used as media streamers for friends. Every one of them reboots itself with screen autorotation on when using either the kk-fire-nexus-rom or the CM-11 for Safestrap ROM. It doesn't always happen immediately, but always within a few minutes of use. None of the LP, MM, or N-based custom ROMs I've tried have ever done this. I'd ideally like to load one of those KK-based ROMs for bluetooth support.
I've prepared each tablet the same way, every time (starting point was always FireOS 4.5.5.1):
1. Root the device and then copy the custom ROM to it
2. Grab the serial/manfid
3. Flash TWRP (either 3.0.2.0 or 3.0.0.1) and the vulnerable bootloader with the dd command
4. Successfully unlock the bootloader
5. From TWRP, wipe everything except internal storage, then install the ROM
6. Wipe cache/dalvik, reboot
This is driving me nuts, since I see users so satisfied with these KK ROMs and little mention of this as an issue. Can anyone see what I'm missing? Thanks.
Click to expand...
Click to collapse
Intriguing - I used this ROM for nearly a year as my daily driver; rock solid with frequent rotations over hundreds of hours. That device (and all other HDXs in my portfolio) never saw FireOS v4; bootloader unlock occured while still on v3. Will be giving this some thought over the next few days.
Davey126 said:
Intriguing - I used this ROM for nearly a year as my daily driver; rock solid with frequent rotations over hundreds of hours. That device (and all other HDXs in my portfolio) never saw FireOS v4; bootloader unlock occured while still on v3. Will be giving this some thought over the next few days.
Click to expand...
Click to collapse
Thanks for the reply. Odd, huh? Though... I did just try ggow's 4.05 ROM and that one autorotates just fine on the Thor I'm currently working on. I'll probably just go with that one or the newer with locked rotation. They're both solid, support Xposed, and app compatibility isn't an issue for my use cases... yet. If only BT wasn't such a challenge on later versions, as that LineageOS ROM is looking really really good...
Never seen that error myself , 5 hdx's unlocked either 4.5.5.1 or 4.5.5.2 all with Nexus KK on them. Another two ready to be unlocked when I've time.
Maybe you've been unlucky and downloaded slightly corrupted files that appear to flash ok. Maybe check the hash value of them ?