I rooted my SM-N9005 with CF-Autoroot and tried installing the hltexx cyanogenmod 11 nightly Rom. First, I flashed Clockworkmod 6.0.4.5 via Odin and put the .zip of the cm rom on the external sd card. When I tried installing the Rom, it failed: This version is for hltexx, you have htle
As far as I read, htle stands for various samsung devices, but htlexx stands for SM-N9005. I looked up my device description in the build.prop:
ro.product.name=hltexx
ro.product.device=hlte
The first attempt to fix this was to simply change the build.prop (which might have been a stupid idea). CWM reported the same problem as before... :/
Then I flashed twrp 2.6.3.7. and tried flashing the cm rom. Not only did it report a problem with the wrong phone model, it also reported that it couldn`t mount drive E (Usbstick).
My next troubleshooting approach was to erase (not delete) the file "metadata", which determines the right device as hltexx. That caused the installation to abort at the point where it usually reports the error... Adapting the metadata to hlte caused the installation to abort, too.
All metadata approaches where done on both cwm and twrp, I also tried restoring the build.prop, so I don`t manually create a difference between the Rom target device and what the ro.product.device tells.
For the sake of it, I also wiped the phone multiple times....without any impact apart from me having to get back old data soon
Someone please help me solve this problem, I did everything I could to get the rom to work. This is my first Android device and attempt to flash a custom Rom, so please don`t laugh at me if I did a stupid mistake somewhere
Ie0n said:
I rooted my SM-N9005 with CF-Autoroot and tried installing the hltexx cyanogenmod 11 nightly Rom. First, I flashed Clockworkmod 6.0.4.5 via Odin and put the .zip of the cm rom on the external sd card. When I tried installing the Rom, it failed: This version is for hltexx, you have htle
As far as I read, htle stands for various samsung devices, but htlexx stands for SM-N9005. I looked up my device description in the build.prop:
ro.product.name=hltexx
ro.product.device=hlte
The first attempt to fix this was to simply change the build.prop (which might have been a stupid idea). CWM reported the same problem as before... :/
Then I flashed twrp 2.6.3.7. and tried flashing the cm rom. Not only did it report a problem with the wrong phone model, it also reported that it couldn`t mount drive E (Usbstick).
My next troubleshooting approach was to erase (not delete) the file "metadata", which determines the right device as hltexx. That caused the installation to abort at the point where it usually reports the error... Adapting the metadata to hlte caused the installation to abort, too.
All metadata approaches where done on both cwm and twrp, I also tried restoring the build.prop, so I don`t manually create a difference between the Rom target device and what the ro.product.device tells.
For the sake of it, I also wiped the phone multiple times....without any impact apart from me having to get back old data soon
Someone please help me solve this problem, I did everything I could to get the rom to work. This is my first Android device and attempt to flash a custom Rom, so please don`t laugh at me if I did a stupid mistake somewhere
Click to expand...
Click to collapse
First of all this is the wrong forum. You are in the ATT Note 3 forum.
Secondly, you don't erase the meta inf folder.
If you want to fix your updater issue, go to the meta inf>com>Google>android and find the updater-script
Send it to me and I will fix it for you so it will install
Sent from my SM-N900A
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Ohh man, i was seriously disappointed in this release. All was good til let CM Updater automatically update the firmware, then all of a sudden my SD card was corrupt.
But wait, i go to "Update from any zip" And my previous installs are there.
4.9.* is corrupt, so i do a nandroid backup and b00m theres HERO... OMFG
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First, this belongs in Q&A and as such has been reported.
But, to be helpful, you can manually flash the system.img and data.img from your backups to make sure that it restores the correct backup via fastboot
If you copy the files to your computer (system.img, data.img, and boot.img) to where-ever you have fastboot then you can run the commands in the bootloader:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
and this should be the same as a NANDROID/switchrom restore.
couple of thing - wrong section
the 4.2.x are stored in /sdcard/cmupdater/ or thereabouts and its unlikely they are all corrupt
its your own fault for not doing a nandroid of a CM (you may have an old one in there if you went to hero after cm and then back again)
if not, start again with 1.6 then CM
CM doesnt screw your sd, improper use does
I am seriously disappointed with your post.
why-o-why do we let people with less than 50 posts create threads anywhere but the QnA?
ZALGO - that was wrecking-crew-esque....let me shake your hand
i miss those guys....
ohh stfu -- all you, i have been flashing PC bios for years, but i "update" my phone with and automatic update, and you jump on my back. and where so you think i got my information to flash my phone. "YES" xda.. so swallow it up.. Question is there a thread for the new Cyanogen 4.12.2 release, if so point me to it. THANKS!!!
fukin look for it you lazy buggar
its staring you in the face...infact it was 2 under your thread when you first posted
and so what if you flash pc bios(s) all the time, this is even easier, you dont even need to push a button until its finished
I'm new with like no post an I can tell your a tool. Do a little search douch nozzle. I am a noob and I agree garok89, no new threads for noobs outside of Q+A before they can show there not tools like this douch who started the tread
cm updater could do with the option to do a Bart / Switchrom / Nandroid backup though.
I have clicked apply now many times and forgotten to manually reboot and do a backup first.
If it fails I just curse myself, but it would be a nice feature.
the cmupdater can easily have the feature to autonandroid - we have the code for it
only problem is, none of the recovery images support it
the second its supported in cyanogens recovery image (and therefore RAs recovery image as it is based on cyanogens) we will enable the feature
reading is the best way to avoid these types of problems.
but lets face it, this is total....
I have to mod some files in /sbin without root before i can root my phone, since it's currently only booting to cwm without working 'adb root', and since it has got at least one corrupt filesystem.
I've tried searching the mounted filesystems of factoryfs.rfs etc, but without success. Where is it?
Would it be possible to update a non-/system directory through an update.zip file? As said, I currently do not have root.
What exactly are you looking for?
I don't really understand your problem.
What ROM are you on right now.
How come you have CWM but not root?
This should it i hope
Joel Sjögren said:
I have to mod some files in /sbin without root before i can root my phone, since it's currently only booting to cwm without working 'adb root', and since it has got at least one corrupt filesystem.
I've tried searching the mounted filesystems of factoryfs.rfs etc, but without success. Where is it?
Would it be possible to update a non-/system directory through an update.zip file? As said, I currently do not have root.
Click to expand...
Click to collapse
Try the following :
Samsung Galaxy S I9000 Custom ROM List
http://forum.xda-developers.com/showthread.php?t=886000
How to root
http://forum.xda-developers.com/showthread.php?t=723596
U need a tool called "ODIN" to root and install most roms
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit : u could also see the videos if u want to here r a few :
http://www.youtube.com/user/TheAndro.../1/ssflhnyzeYc
http://www.youtube.com/watch?v=LjBEBvRVRYs
http://www.youtube.com/watch?v=2O8KT...eature=related
"What ROM are you on right now.
How come you have CWM but not root?"
I'm currently using XXJP3 without the /media and /app directories(I mounted the factoryfs.rfs on my computer and moved them elsewhere.)
adb root has worked for me earlier, but suddenly, it stopped. Instead i get the
error: device not found
error when issuing adb shell after adb root.
The problem is, I cannot install root or anything else yet because my /system(stl9) partition does not act the way it should.
No factoryfs containing /media and /app can be flashed. I've tried the --repartition flag(with correct .pit-file.)
To work around it, I'm trying to edit a script, located in /sbin, to be run at boot. The script will hopefully allow me to fix the partition with root privileges. In either case, it will be able to write the output to a log file to be read through $-adb shell.
The /sbin boot script would also allow me to use the external sd instead of the internal memory in case the stl9 partition somehow cannot be fixed.
As rooting is no option yet, I need to flash the /sbin directory, but since I can't find it in the rom, I need your help here.
When I flash back to stock, of course the new updated market works. At one point I kept the stock and flashed a new kernal after updating to the current 2.2 and still the new market worked. As soon as I flash a custom ROM such as Serendipity, Fasty, Cognition, or another the market all of a sudden does not work. When I mean does not work, I only mean in the instance that it will not download large apps. I have read on flashable zips, adb shell commands, and other methods such as removing the battery but still none of this works. Is there any way to fix this problem without reverting to the old market??
It's cache size related bug, the problem here is that manufacturers put a cache partition on their devices that is smaller than googles maximum allowed app size for the market, 50MB (which was updated this year from 30mb). Reverting back to the old market will fix that issue and what I'd recommend you is to freeze MarketUpdater in TiBu (titanium backup app) so that it won't allow it to update itself back to the new market.
In case u want to use the new market, u'll have to apply the fix made by corgar - iXNyNe ,but it requires a kernel with init.d script support. If u wanna try it out here's the script, download and extract the file and then copy it in system/etc/init.d folder with a root explorer and modify the permissions of the script to 7-5-5. To do that go to system/etc/init.d folder ,mount r/w (if ur using root explorer) and long press on S95change_cache file, select permissions and make it look like in the pic below and then reboot ur phone in recovery and wipe cache ,dalvik cache and restart ur phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If all went well (u should have a cache.img file under dbdata of 54+ mb) u now can download all the apps from the new market, if it didn't then try with 7-7-7 permissions (like in the pic above only everything checked)
There are other methods , here's a post from Kyuta Syuko that sums it all up. http://forum.xda-developers.com/showpost.php?p=17850944&postcount=9050
Have u tried stopping the market and clearing all data in the all apps menu?
Sent from my SGH-I897 using xda premium
He can try that too, but that's useful when ALL downloads aren't starting/apps aren't updating. But the 30mb+ download issue ,insufficient space error, is cache related.
I can confirm (and others did as well) that the script works.
Thanks for the help but I did search like I posted. None of the options worked. But I did figure out a way around it. Just disable the VooDoo Lagfix and system lagfix. Download perfectly afterwards. Defintely beats reverting to older markets and the methods described. Although this worked for me, hopefully someone will find luck with the methods you all posted. But yeah I tried everything besides reverting to the market and enabling a script change. That was going to be my last option.
Good to hear u managed to get it work, btw could u pls check if Third Blade downloads without an error. Thx
Hi,
There is this bug on LOS16 that if the pop up camera is up and then the device switches off, the camera stays up permanently until a stock rom is reflashed. I had this issue before, so I restored a backup I made on MIUI 10.3.16 using TWRP, but the device was stuck in a bootloop, and the camera was still stuck, so after restoring different backups I made, I decided to finally use MiFlash to fastboot flash MIUI 10.3.16, and I chose the 'keep user data' option, however this also bootlooped and went into MIUI recovery. I reflashed TWRP and now I face this issue:
TWRP does not recognise that my phone is encrypted, and does not ask for my password, so I can see that my files are here, but they have random folder and file names. (example shown below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I managed to get MIUI running, however it does not ask me for my password, only my Mi account password.
I restored a LOS16 backup I made ages ago, and that also does not ask me for my password - the files I see in the file manager are all encrypted like TWRP.
I attempted the 'twrp decrypt' command, but that does not work either.
I attempted flashing backups and custom roms from a USB, using PitchBlack recovery, OrangeFox, and two TWRP versions.
All I want is for either a recovery or a rom to ask for my unlock password, so it can use that to decrypt my files.
I am not 100% sure if using MiFlash is what caused this, but is there anything else I could try? Are all my files gone? I cannot copy my encrypted files over to my PC and Windows returns an error when trying to do so. Are there any 3rd party tools I can use to decrypt my stuff?
I know I could just wipe my storage and start again, but I do not really want to do that until I know for sure that my files are gone.
I was thinking that MiFlash wiped the decryption keys from my device, but wouldn't a backup restore them?
If it is not possible to save my files, could someone explain why, so I do not make the same mistake again?
Any help would be appreciated.
Format Data, you cant go from miui to aosp or vice versa without doing that. backup your data to pc before or whatever cuz it wipes all internal.
Best thing to do is to fastboot flash again, but use the clean all option.
It's never a good idea to dirty flash when doing anything other than updating a ROM. You might sometimes be OK if flashing from one AOSP ROM to another AOSP ROM.
If your going from MIUI to a custom ROM, or from a custom ROM to MIUI, then it's not worth the aggro you'll most likely get by dirty flashing. Just spend the extra time backing up your data and save the headache.
As for the data, try installing a different TWRP and see if that will then ask for a password to decrypt the phone, before you do a clean install of MIUI.
I've followed the process outlined here. After installing the ZIP, it rebooted, but went back to recovery. When I said reboot system, it said No OS installed.
So, I tried to start over by formatting data and then copying the zip again via ADB Push. Then the trouble starts. After adb push, which takes about 5 minutes, it says
Code:
failed to copy 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip' to '/sdcard/xiaomi.eu.zip': write failed: No space left on device
After that, the data partition seems corrupted. Whenever I go to Install, it shows 0 bytes. Upon Googling I found a solution by formatting to ext2 and back to ext4. Then, it shows again as 100000MB. However, adb push every time fails with same problem.
For some weird reason, I can push to /data. But still running into same problem after installing ROM and rebooting, it goes back into recovery.
I also tried to sideload, but then I run into this issue:
Code:
D:\Tools\ROMs>adb sideload xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip
loading: 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip'
* cannot read 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip' *
So, I'm stuck with a device without any ROM. Any suggestions please?
Did you ask in the MIUI EU forums as well? Since there would be more ppl familiar with these issues than here.
I'm also interested in this since I prefer EU roms. Also you need a specific TWRP version which I believe is still in alpha stage for the 10 Pro since its still a new device. There should be a TWRP thread somewhere here where you can also ask.
I just got my 10 pro and need to wait a few more days to unlock BL, then I will be flashing an EU rom, hence my interest. Hope you find a solution.
Use TWRP from here:
https://forum.xda-developers.com/t/4248449/
fastboot reboot bootloader
fastboot boot TWRP_file_name.img
Format Data, type yes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reboot to recovery.
The internal storage should be visible.
Connect phone to PC and put ROM into phone.
Flash ROM, format data, yes
Reboot to system.
If above not work, make your phone under fastboot mode, Mi-Flash, and flash your stock fastboot MIUI. Don't lock your bootloader.