Related
I wanted to write this "guide" for all the others that may be experiencing issues such as myself and others that I've talked to and helped. It was quite a learning experience and one of those "wow, I totally screwed myself" moments, to say the least lol.
There have been quite a few posts by others that outline how to update your rooted phone with the OTA but I wanted to put it down a bit more step by step with some extra information for those that thought it might be a good idea to just DELETE some apps from the /system/app patition (myself, included) without taking a full system backup using CWM, etc. I do NOT believe that a Titanium backup is sufficient if you choose to delete the application afterwards (as I see no evidence that the [required] .odex files are part of the TiBu backups)
Due to all the requests (here is my RAZR /system/app dump):
Pre-OTA: http://bit.ly/vwkbDw
Post-OTA: http://bit.ly/rZdQgC
So here we go...
1. Settings -> About Phone -> System Updates -> "Download Now"
2. Once downloaded, choose "Install Later" (important!)
3. Open up ES File Explorer or Root Explorer or you can even use adb to shell into the system (not recommended unless you're really good at this)
4. Browse to the /cache directory
5. Copy the two files named "Blur_Version.6.11.744.XT912.Verizon.en.US.crc" and "Blur_Version.6.11.744.XT912.Verizon.en.US.zip" to the /sdcard-ext location (NOT /sdcard)
6. Download and Install (from the Market) "OTA RootKeeper"
7. Run OTA Rootkeeper and select "Protect Root" (this will preserve files and links to the root application after the update). You CAN still choose to re-root using DoomLord/Zerg method but this is a LOT easier
8.You can choose to backup your apps via TiBu if you want to be extra cautious should something go wrong (but not required).
9. Power OFF the device. Then enter Motorola Recovery mode (Hold Vol+ and Vol- and Power). Click Vol- to highlight Recovery Mode and Click Vol+ to select it. Wait for the Triangle and exclamation point and then press both Vol buttons at the same time
10. Choose to "apply update from sdcard" by using the the Vol+ or Vol- to highlight and the Power Button to select
11. Choose the update file using the same method as step 10
12. Let it run and do it's thing...here's where the problems can start. If you have no problems you can skip to step 18
13. If you receive a "Status 7" error message it is probably complaining about checksum mismatch of the file that is ALSO listed in that output. This can also happen if the file is missing
14. Record the first 4 characters of the TWO checksums that it lists (this is important, do not forget) AND the filename (usually /system/app/<somename.apk> /system/app/<somename.odex>
Having these checksums will help you locate which file you need to get you back to "good" standing. The first value indicates the SHA1 checksum of the UPDATED file (POST OTA patching) while the second value indicates the SHA1 checksum of the older file (PRE OTA patching). There are quite a few resources on these forums where people have provided their "system dump".
You can also find this information after an unsuccessful install in the /cache/recovery/last_log directory on your phone - for those that use the install method from within the Android OS (Automatic OTA Install)
15. Download one or more of these "system dumps" and extract the file named in the error. Copy it to your sdcard and then use Root Explorer or Astro to copy it to the /system/app location (you might need to make it R/W on /system/app)
15A. For the advanced users:
You can save some guess work and get the sha1 value using a utility (windows/linux) to compare the strings with what was in the error message.
IF the checksums match you might as well copy over the corresponding .odex/.apk file as well.
IF the checksums do NOT match, you might as well scrap that "system dump" and download another one (and pray)
15B. IF you are unable to locate an original razr file that matches your criteria you can also take a stab and ask someone to send you their POST-OTA file(s) that you are missing. You can also compare the SHA1 checksum OR just try and see if it works. The installer will continue forward if it detects either the CORRECT old or new file already in place (*whew*)
16. Then return to step 9. Continue steps 9-15 until the update goes through.
18. Reboot after the update is complete
19. Verify the update was successful by following step 1 (there are other ways to see the version as well)
20. Re-run OTA RootKepper and select the option to "Restore Root"
21. Disconnect any USB cable to the phone and reboot. Verify root works properly (SetCPU, TiBu, SuperUser App, etc)
IF you are unable to regain root via Step 20, then you can always use the method that you previously used to RE-root your phone (Zert/DoomLord utility)
22. FREEEEEZE your apps from now on. (at least until there is an SBF). Stop deleting anything that isn't on your sdcard-ext partition
I hope that helps some folks out. I had about 8 files to replace and it seemed that there was never a "system dump" that had all of them. I helped one user by providing just ONE file that he accidentally deleted. In turn, after the update he provided me with both (updated) files that I needed. Win-Win!
I have my old and my NEW "system-dump" files so don't hesitate to ask me for them. If I receive enough requests I will end up putting them on one of the mediafire/megaupload places. A few other places to get the system dumps are from some of the ROMS provided for the US RAZR (i had some files match from the RAZRX 1.0 ROM)
If you noticed that I skipped number 17 then you were paying close enough attention ;-)
It worked, thank you.
Sent from my DROID RAZR using xda premium
great write up
droidony--droidforums
I cant find any dump links that are active. My problem is with the settings.apk. can anyone help?
Found one dump and no match.
When I looked in my cache thingy there wasn't anything there. Am I missing something or looking in the wrong spot?
I originally needed the maps odex file (as that was what was showing up in the log but I had it on my phone I must have done something as to how it disappeared) which i got from your download well one thing had lead to another with all these zips of the update and this is where I am at now. I guess I will stop here until I get better direction on what to do now. I am not sure if it is better or worse than before. This is the current log of where I am. If you know where to go from here please let me know. Thanks!
Parsing the directoryd_name: 3-0:1.0
Parsing the directoryd_name: 2-1
Parsing the directoryd_name: 2-1:1.0
Finding update package...
I:Update location: /cache/Blur_Version.6.11.744.XT912.Verizon.en.US.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Verifying current system...
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop", "88b14d106c1935ebf67d34285a6840e9fc4a77da", "84e1256862a5723b93d38b6135ce947e97a39504")
assert failed: apply_patch_check("/system/build.prop", "88b14d106c1935ebf67d34285a6840e9fc4a77da", "84e1256862a5723b93d38b6135ce947e97a39504")
E:Error in /cache/Blur_Version.6.11.744.XT912.Verizon.en.US.zip
(Status 7)
Installation aborted.
-------------------------------------------------------------------------------------
update: I tried to install the 744 copy that was on the sd card and this is the error it gave me. The above is the error it gives me directly from the ota download and update.
-- Install /sdcard/download ...
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Failed to mount /dev/block/mmcblk1p20 on /system: Device or resource busy
mtd mount of system failed: Device or resource busy
script aborted: assert failed: mount("ext3", "MTD", "system", "/system")
assert failed: mount("ext3", "MTD", "system", "/system")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
I:Set boot command ""
elyhlapetina said:
When I looked in my cache thingy there wasn't anything there. Am I missing something or looking in the wrong spot?
Click to expand...
Click to collapse
Same here. No files there.
elyhlapetina said:
When I looked in my cache thingy there wasn't anything there. Am I missing something or looking in the wrong spot?
Click to expand...
Click to collapse
Oaklands said:
Same here. No files there.
Click to expand...
Click to collapse
If you don't have root enabled you won't be able to view the folder contents. SO, if you used the OTA RootKeeper app and temporarily removed root, you will need to back into that application and restore root...
Viewing the last_log in the /cache/recovery location isn't needed, if you do the manual installation using the Motorola Recovery. The same error messages appear in the yellow text after the update fails and before you reboot the phone.
branshaw09 said:
I cant find any dump links that are active. My problem is with the settings.apk. can anyone help?
Found one dump and no match.
Click to expand...
Click to collapse
Branshaw, did you take a look at my two download options listed in my original post? Settings.apk SHOULD be in there. You can also try grabbing one from one of the few ROMS that are out for the RAZR - i suggest trying to pull the apk from the RAZRX 1.0 ROM
kb3awq said:
I originally needed the maps odex file (as that was what was showing up in the log but I had it on my phone I must have done something as to how it disappeared) which i got from your download well one thing had lead to another with all these zips of the update and this is where I am at now. I guess I will stop here until I get better direction on what to do now. I am not sure if it is better or worse than before. This is the current log of where I am. If you know where to go from here please let me know. Thanks!
Parsing the directoryd_name: 3-0:1.0
Parsing the directoryd_name: 2-1
Parsing the directoryd_name: 2-1:1.0
Finding update package...
I:Update location: /cache/Blur_Version.6.11.744.XT912.Verizon.en.US.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Verifying current system...
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop", "88b14d106c1935ebf67d34285a6840e9fc4a77da", "84e1256862a5723b93d38b6135ce947e97a39504")
assert failed: apply_patch_check("/system/build.prop", "88b14d106c1935ebf67d34285a6840e9fc4a77da", "84e1256862a5723b93d38b6135ce947e97a39504")
E:Error in /cache/Blur_Version.6.11.744.XT912.Verizon.en.US.zip
(Status 7)
Installation aborted.
-------------------------------------------------------------------------------------
update: I tried to install the 744 copy that was on the sd card and this is the error it gave me. The above is the error it gives me directly from the ota download and update.
-- Install /sdcard/download ...
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Failed to mount /dev/block/mmcblk1p20 on /system: Device or resource busy
mtd mount of system failed: Device or resource busy
script aborted: assert failed: mount("ext3", "MTD", "system", "/system")
assert failed: mount("ext3", "MTD", "system", "/system")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
I:Set boot command ""
Click to expand...
Click to collapse
It sounds like you ran something on your phone that may have adjusted settings in the build.prop file (supercharger, jakebitesmod, etc). I can try and give you a copy of mine when I get home tonight, but hopefully someone else in here would be kind enough to attach it to a post on this thread.
it worked!!
thank you so much it worked perfected
Great solution, but what if I just have to restore an app (Facebook Authenticator in this case) I'm already Post-OTA, deleted it by accident, any help please? been scratching my brain for days. TIBU just hangs when I try to restore it.
jerkwad said:
It sounds like you ran something on your phone that may have adjusted settings in the build.prop file (supercharger, jakebitesmod, etc). I can try and give you a copy of mine when I get home tonight, but hopefully someone else in here would be kind enough to attach it to a post on this thread.
Click to expand...
Click to collapse
Actually I haven't ran anything extra just copied the map codex in with the others and the pre and post update on here gives signature verification error lie the other couple I tried from droid forums from the other guy who had a zip for a solution which was a stock root zip. This is amazing my Droid 1 could flash anything etc. And I was trying to be a stock good boy with this phone except root.
can someone please help me on what to do now. after i got to trying to install the update i recieved the status 7
this is what my phone said
assert failed: apply_patchcheck("system/app/livewallpappers.apk", "37db550d10330f4e0bcf0efb60a86b62f7598a4a3", "d3686011083bcb1b46cb9d1702b1788bf5772e37")
E:error in /tmp/sideload/package.zip
(status 7)
Installation aborted
So I took a look at what was missing, and it doesn't match with the directions you gave. Atleast I don't think it does.
here's what i got:
--Install /sdcard/Android Dev Update ...
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/preinstall/KnowYourDevice/Motorola_XT912_BatterySave.3gp",
5faf882a9f143c2e45a264aad9c067233a43be8b", "6bcc903965d9cd3862f5c5a5760e129d36b07cf5")
E:Error in /tmp/sideload/package.zip
(status 7)
Installation aborted.
I didn't, myself, remove or freez any apps.
jerkwad said:
Branshaw, did you take a look at my two download options listed in my original post? Settings.apk SHOULD be in there. You can also try grabbing one from one of the few ROMS that are out for the RAZR - i suggest trying to pull the apk from the RAZRX 1.0 ROM
Click to expand...
Click to collapse
I am trying to download your pre ota file now. The settings.apk md5sum in razrx ROM fine match my error report
I have the same problem. Im rooted and use astro file manager and nothing is in cache.
Sent from my DROID RAZR using xda premium
I have same issue with guidedtours.odex
checksum first 4 are
64d7
1c18
5bb6 & 5cc1
Sent from my DROID RAZR using xda premium
95ea and b39c for gmail.odex any info greatly appreciated.
HDW
Hallo, after two days of trying to make kexec working, got it working! Its based on hard boot kexec! We can create now multiboot menu and boot multi roms without need for flashing them! Will make this thread updated including files, kernel and instructions!
munjeni said:
Hallo, after two days of trying to make kexec working, got it working! Its based on hard boot kexec! We can create now multiboot menu and boot multi roms without need for flashing them! Will make this thread updated including files, kernel and instructions!
Click to expand...
Click to collapse
and probably now guys with locked bootloader can boot roms requiring custom kernels
DevSwift1 said:
and probably now guys with locked bootloader can boot roms requiring custom kernels
Click to expand...
Click to collapse
NO because kernel need enabled kexec and reguire some other modifications whick is not exist on stock kernel!!!
Tried to boot stock kernel but failed, seems not stable kexec by now! Need help!
Here is kernel changes (3 commits by Aug.09.2013) -> https://github.com/munjeni/android_kernel_xperiago/commits/jb-dev seems there is problem with clean reboot! Got kexec working with usind zImage from the same kernel version but seems when there is another kernel version its fail! I think it fail on my reboot function implementation! Need help to solve these things!
Got ansfer by self. Stock kernel and everyother without kexec patch ca not be loaded more info here -> http://forum.xda-developers.com/showthread.php?p=44077327
Tomorow will make it better, hope perfectly working.
Ok, lets go multiboot development!
My experience using kexec:
- since hard reboot owerwrite new kernel and ramdisk, I disabled hard reboot. So we need shutdown cpu instead of using function reboot! Since we have no shutdown cpu function we have very slow boot after executing new kernel and ramdisk (curently I am satisfied with slow boot because kexec can boot new kernel and ramdisk, yes its slow but working )
What is needed for kexec boot:
- kexec can not boot non kexec based kernels
- kexec can boot only kexec enabled kernel which mean only kernel which have my kexec patch (you can patch your kernel using kexec patch from my git)
- suported phones by now is only Sola and Go
My idea for multiboot by now:
- making boot menu based on modified CWM recovery
Modified CWM recovery plan:
- create new recovery and add new sub menu for multiboot feature
CWM multiboot menu idea:
- here we can write kexec multiboot functions
CWM kexec function idea:
- mount system, cache, userdata partition from external sdcard EXT4 partitons and mount them (only if these partions is created by you on your sdcard !!! We can create an small submenu for creating these partitons if these partitons not exist, but not now, we can do it later after creating simple kexec main menu))
- after mounting these partitions we can:
- boot android from allready installed android from these partitions
- ability to install new android to these partiton and boot them
Lets go! Before I start making new CWM, I need better ideas! What you think how we can do it??? Waiting your ideas!!!
Maybe we can do it without using CWM???
So, how about another kernel or rom which isn't supporting kexec yet?
Sent from risahikari
munjeni said:
Lets go! Before I start making new CWM, I need better ideas! What you think how we can do it??? Waiting your ideas!!!
Maybe we can do it without using CWM???
Click to expand...
Click to collapse
I cannot think of a way to do this without involving CWM. But we could make use of the volume buttons to select the ROM on boot (by mounting the appropriate partition based on the volume button that has been pressed down when the bootsplash screen is displayed). However this would limit us to the number of ROMs that can be installed to two (or max 3, if we have an option to set a default ROM to boot if no button is pressed).
Brilliant work by the way. You are Godlike! :victory:
itachilinux said:
So, how about another kernel or rom which isn't supporting kexec yet?
Sent from risahikari
Click to expand...
Click to collapse
Simple not supported!
First of all we need to create ramdisk which will boot android located on external sdcard, than if we get it working we can play with kexec. I need your help! If some one get android working from external sdcard than I will continue further. I am allso playing now with new ramdisk and trying to get external android booting!!
Our multiboot is not ready. Only ready is kexec tool and kexec kernel. Our multiboot feature is not yet implemented. Our multiboot is in plan and our multiboot need ideas!
can this be of any help?
http://forum.xda-developers.com/showpost.php?p=42057833&postcount=1
github:
https://github.com/tux-mind/tf201-dev
Changed fstab, recovery.fstab and sony fstab device paths to point to the external sdcard partition, modified updater_script paths, rebooted to the recovery, installed rom to the external sdcard partitions, rebooted, after abnormaly slow boot system booted but is abnormally unresponsive, so I deleted and reverted back to the emmc boot. Sory guys I am stopping here until some one get android booted from sdcard! I have no free time to play with external boot. When you done it I will continue
Any one have idea what is use of the fota kernel??? Got fota kernel and ramdisk kexeced and booted, found some tools in sbin folder, there is fota tools, for example after exacution of the fota-ua got this output:
./fota-ua --help
FOTA-UA May 21 2013 18:05:10
ERROR [181] Parameter Error
Info [745] No status file
Total physical memory: 407695360 bytes
Total available physical memory: 8314880 bytes
Configuration information at runtime:
The number of pages of physical memory SC_PHYS_PAGES: 99535
The number of currently available pages of physical memory _SC_AVPHYS_PAGES: 203
0
Info [88] The number of processors configured _SC_NPROCESSORS_CONF: 2
The number of processors currently online (available) _SC_NPROCESSORS_ONLN: 2
Size of a page in bytes _SC_PAGESIZE: 4096
Logging of resource usage measures:
Maximum resident set size ru_maxrss: 172 KB
Page reclaims ru_minflt: 84
Page faults ru_majflt: 0
Block input operations: 0
Block output operations: 0
Info [468] No sdcard found in mounts
Info [757] Update Failed
WARN [48] Failed to remove /sbin/fota-ua, Read-only file system
WARN [52] Failed to remove /sbin/fota-mke2fs, Read-only file system
WARN [56] Failed to remove /sbin/rb_repart, No such file or directory
Click to expand...
Click to collapse
What we can do with these tools???
Or another tool:
./rb_repart
Repartitioning Tool
(C) Copyright 1999-2011 Red Bend Ltd.
4 Hacharash St. Hod-Hasharon, Israel
Version: 7.0.15.5514
Usage: ./rb_repart
-r [OPTIONAL, DEFAULT] - Run full operation
-t [OPTIONAL] - Run in test mode. Do not perform writes
-c config_file [OBLIGATIONAL] - Configuration file
Click to expand...
Click to collapse
munjeni said:
Any one have idea what is use of the fota kernel??? Got fota kernel and ramdisk kexeced and booted, found some tools in sbin folder, there is fota tools, for example after exacution of the fota-ua got this output:
What we can do with these tools???
Or another tool:
Click to expand...
Click to collapse
Well have you ever updated Sola with OTA,you will notice it boots to recovery and thats fota kernel "f-ota" - friendly over the air update system
XperianPro said:
Well have you ever updated Sola with OTA,you will notice it boots to recovery and thats fota kernel "f-ota" - friendly over the air update system
Click to expand...
Click to collapse
When I tried on Xperia Go to update trought fota it was not worked! I never seen anything related to the fota recovery! Is recovery exist on fota kernel??? Have any menu???
Found some logs:
/data/local/tmp/sbin/fotatools # find / | grep fota
find / | grep fota
/cache/recovery/fota
/cache/recovery/fota/executed
/cache/recovery/fota/report
/cache/recovery/fota/status
/system/bin/fota-snoop
find: /proc/2652: No such file or directory
find: /proc/3172: No such file or directory
find: /proc/3554: No such file or directory
find: /proc/3610: No such file or directory
find: /proc/3723: No such file or directory
find: /proc/3884: No such file or directory
/data/local/tmp/sbin/fota-tad
/data/local/tmp/sbin/fotatools
/data/local/tmp/sbin/fotatools/rb_repart
/data/local/tmp/sbin/fotatools/vold.fstab
/data/local/tmp/sbin/fotatools/toolbox
/data/local/tmp/sbin/fota-mke2fs
/data/local/tmp/sbin/fota-ua
/dev/.fota_ui_down
/dev/.fota_ui_shutdown
/data/local/tmp/sbin/fotatools # ls /cache/recovery
ls /cache/recovery
fota
last_log
/data/local/tmp/sbin/fotatools # ls /cache/recovery/last_log
ls /cache/recovery/last_log
/cache/recovery/last_log
/data/local/tmp/sbin/fotatools # cat /cache/recovery/last_log
cat /cache/recovery/last_log
MR: Master reset starting Sat Aug 10 20:26:26 2013
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /data ext4 /dev/block/mmcblk0p11 (null)
2 /cache ext4 /dev/block/mmcblk0p12 (null)
3 /modemfs ext4 /dev/block/mmcblk0p6 (null)
MR: Got content --wipe_data from /cache/recovery/command
MR: Formatting /cache
Creating filesystem with parameters:
Size: 262144000
Block size: 4096
Blocks per group: 32768
Inodes per group: 8000
Inode size: 256
Journal blocks: 1024
Label: /cache
Blocks: 64000
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16000 inodes and 2065/64000 blocks
MR: Formatting /data
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label: /data
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
MR: Unlocking gesture
MR: Resetting RFHAL parameters
MR: Cleaning dir /modemfs/RFHAL
MR: Leaving dir /modemfs/RFHAL
MR: Master reset done
/data/local/tmp/sbin/fotatools #
Click to expand...
Click to collapse
I hope it will work on Xperia™ U, I don't know if it could be possible as I don't know how many differences are between Sola's and U's ramdisk and stuff. :/
munjeni said:
Any one have idea what is use of the fota kernel??? Got fota kernel and ramdisk kexeced and booted, found some tools in sbin folder, there is fota tools, for example after exacution of the fota-ua got this output:
What we can do with these tools???
Or another tool:
Click to expand...
Click to collapse
well, on xperia s for example we use fota partition like a it was a recovery partition
otherwise as soon as you unlock your bl (= no more OTA) it becomes usless
mirhl said:
well, on xperia s for example we use fota partition like a it was a recovery partition
otherwise as soon as you unlock your bl (= no more OTA) it becomes usless
Click to expand...
Click to collapse
How you load recovery from ota partition? Seems you have something like LK bootloader???
munjeni said:
How you load recovery from ota partition? Seems you have something like LK bootloader???
Click to expand...
Click to collapse
a sort of
newer kernels when booting recovery, check if FOTA partition has the custom one installed
if yes, they loads that. otherwise standard recovery
more information here
mirhl said:
a sort of
newer kernels when booting recovery, check if FOTA partition has the custom one installed
if yes, they loads that. otherwise standard recovery
more information here
Click to expand...
Click to collapse
Thats good idea, but thats not ideal solution in comparation with phones which have separated recovery/boot partition and bootloader ui like HTC devices which have direct recovery load trought bootloader, these solution only working if primary boot partition is modified and added "few lines" for booting recovery from seccond partition (like ota partition). Will be perfect solution if we make LK bootloader for separating recovery/boot partition, allso with LK we will be able to create custom emmc layout, by now I can not see any small bootloader for NovaThor on google search, seems thats not public. Searching for a way for creating bootloader based on kernel. How we can modify curent kernel and make them bootloader??? We can modify recovery and make them bootloader kexec based, but I am not happy with kexec because we need to fix them first because loading an kernel trought current kexec patch is very slow! I will be happy if some one look into my git and find a solution for fixing them!
mirhl said:
well, on xperia s for example we use fota partition like a it was a recovery partition
otherwise as soon as you unlock your bl (= no more OTA) it becomes usless
Click to expand...
Click to collapse
What about if I relock my bootloader, do I will be able to use fota??? Seems ota working only if drm keys is not broken??
munjeni said:
What about if I relock my bootloader, do I will be able to use fota??? Seems ota working only if drm keys is not broken??
Click to expand...
Click to collapse
i have a locked bootloader but on xperia u and if you want anything i will happly help and mine has never been unlocked
---------- Post added at 04:59 PM ---------- Previous post was at 04:44 PM ----------
bobthecooldad said:
i have a locked bootloader but on xperia u and if you want anything i will happly help and mine has never been unlocked
Click to expand...
Click to collapse
just read this about fota
http://forum.xda-developers.com/showpost.php?p=12615775&postcount=1
and the orginal file is checked and if it isnt the correct one the phone wont boot
[Recovery] Working CWM 6.0.2.8 & CWM 6.0.3.7 for Samsung Galaxy Star ( S5280 &S5282 )
Hey guys,
We got another victory. CWM 6.0.2.8 & CWM 6.0.3.7 has been released for our device galaxy star.
STATUS - Tested
Use at your own risk i will not responsible for any mishappening
Contributor :
@Doc_cheilvenerdi.org
Procedure -
i) Boot your phone in odin mode.
ii) Then open odin.
iii) Flash it & Enjoy.
Link - CWM 6.0.2.8 - https://drive.google.com/folderview...sp=drive_web&tid=0B3qe_9NlA1D_Q2RTRzVBRmFkeDA
CWM 6.0.3.7 - https://drive.google.com/folderview?id=0B3qe_9NlA1D_c3dmNm1yQzdyX2M&usp=drive_web
Here is the screenshot-
did u test it?
Pleas Hold on and read carefully!
Please Hold on!
No Release yet!
Releasing software is a long and hard process...
...actually my Phone is on Jellybean 4.1.2 but I don't have yet a local copy of my european archive due to hotfile.com shutdown...
...so I'm still waiting for a mirror to back it up:
it's a strong option to recover a phone from a soft brick...
So what I'm doing here now?
I build Cyanogenmod from long time ago... starting with Gingerbread 7.2 up to KitKat 11.0 (for me it's really a different beast from older ones...)...
Now i prepared a device Skeleton for my mintss phone, I populated it looking online (many thanks to Ankur850, Batman38102, Requisite0, Sakindia123, TeamRegular and many others) and followed the Cyanogenmod guidelines to build a CWm recovery...
And I built a 6.0.2.8 (tuned to Cyanogenmod 10.0) with a working Kernel, a simple ramdisk, and so on...
...But I didn't test it yet...
...I'm still waiting due to my lack of a full firmware archive...
I also tried - for fun - to build the CWM 6.0.4.5 for Cyanogenmod 11.0 (beware: just a Blind Shot)
...using the 10.0 Kernel... working kernel but wrong configuration: it lacks Selinux capabilities (Working on it right now)...
...using a ramdisk tuned to JellyBean...
...filesystem nor permissive neither enforced...
..etc...
All things which can lead to a disaster while testing...
So, please, hold on until I'll test it on my own phone...
...if everything will be fine I'll be really happy to share it for the community...
See you soon on this thread then...
...news scheduled on incoming new year...
Doc_cheilvenerdi.org said:
Please Hold on!
No Release yet!
Releasing software is a long and hard process...
...actually my Phone is on Jellybean 4.1.2 but I don't have yet a local copy of my european archive due to hotfile.com shutdown...
...so I'm still waiting for a mirror to back it up:
it's a strong option to recover a phone from a soft brick...
So what I'm doing here now?
I build Cyanogenmod from long time ago... starting with Gingerbread 7.2 up to KitKat 11.0 (for me it's really a different beast from older ones...)...
Now i prepared a device Skeleton for my mintss phone, I populated it looking online (many thanks to Ankur850, Batman38102, Requisite0, Sakindia123, TeamRegular and many others) and followed the Cyanogenmod guidelines to build a CWm recovery...
And I built a 6.0.2.8 (tuned to Cyanogenmod 10.0) with a working Kernel, a simple ramdisk, and so on...
...But I didn't test it yet...
...I'm still waiting due to my lack of a full firmware archive...
I also tried - for fun - to build the CWM 6.0.4.5 for Cyanogenmod 11.0 (beware: just a Blind Shot)
...using the 10.0 Kernel... working kernel but wrong configuration: it lacks Selinux capabilities (Working on it right now)...
...using a ramdisk tuned to JellyBean...
...filesystem nor permissive neither enforced...
..etc...
All things which can lead to a disaster while testing...
So, please, hold on until I'll test it on my own phone...
...if everything will be fine I'll be really happy to share it for the community...
See you soon on this thread then...
...news scheduled on incoming new year...
Click to expand...
Click to collapse
excelent will wait for it :good:
I cant test it
Chirtagh said:
did u test it?
Click to expand...
Click to collapse
I cant test it bcoz i have S5282.:crying:
Download stock firmware
Doc_cheilvenerdi.org said:
Please Hold on!
No Release yet!
Releasing software is a long and hard process...
...actually my Phone is on Jellybean 4.1.2 but I don't have yet a local copy of my european archive due to hotfile.com shutdown...
...so I'm still waiting for a mirror to back it up:
it's a strong option to recover a phone from a soft brick...
So what I'm doing here now?
I build Cyanogenmod from long time ago... starting with Gingerbread 7.2 up to KitKat 11.0 (for me it's really a different beast from older ones...)...
Now i prepared a device Skeleton for my mintss phone, I populated it looking online (many thanks to Ankur850, Batman38102, Requisite0, Sakindia123, TeamRegular and many others) and followed the Cyanogenmod guidelines to build a CWm recovery...
And I built a 6.0.2.8 (tuned to Cyanogenmod 10.0) with a working Kernel, a simple ramdisk, and so on...
...But I didn't test it yet...
...I'm still waiting due to my lack of a full firmware archive...
I also tried - for fun - to build the CWM 6.0.4.5 for Cyanogenmod 11.0 (beware: just a Blind Shot)
...using the 10.0 Kernel... working kernel but wrong configuration: it lacks Selinux capabilities (Working on it right now)...
...using a ramdisk tuned to JellyBean...
...filesystem nor permissive neither enforced...
..etc...
All things which can lead to a disaster while testing...
So, please, hold on until I'll test it on my own phone...
...if everything will be fine I'll be really happy to share it for the community...
See you soon on this thread then...
...news scheduled on incoming new year...
Click to expand...
Click to collapse
Bro here is link to your country stock firmware & its not on hotfile.
http://terafile.co/5a3646396569
hey
rahulsinghal said:
I cant test it bcoz i have S5282.:crying:
Click to expand...
Click to collapse
umm i dont think this cwm is only compatible for s5280
you can try it
even if it doesnt work,it wont give you a bootloop,just a cwm error which can be recovered easily by flashing stock recovery
link
rahulsinghal said:
Hey guys,
We got another victory. CWM 6.0.4.5 has been released for our device galaxy star.
STATUS - Untested
Use at your own risk i will not responsible for any mishappening
Contributor :
@Doc_cheilvenerdi.org
Link - https://docs.google.com/file/d/0B3qe_9NlA1D_bm5WbDc2YWM3ck0/edit
Click to expand...
Click to collapse
the download link is denying access :/
hmmm
swhackeristahsan said:
the download link is denying access :/
Click to expand...
Click to collapse
Hey just request that file after some minute you will get access. n whats going on akshaymod
Doc_cheilvenerdi.org said:
Please Hold on!
No Release yet!
Releasing software is a long and hard process...
...actually my Phone is on Jellybean 4.1.2 but I don't have yet a local copy of my european archive due to hotfile.com shutdown...
...so I'm still waiting for a mirror to back it up:
it's a strong option to recover a phone from a soft brick...
So what I'm doing here now?
I build Cyanogenmod from long time ago... starting with Gingerbread 7.2 up to KitKat 11.0 (for me it's really a different beast from older ones...)...
Now i prepared a device Skeleton for my mintss phone, I populated it looking online (many thanks to Ankur850, Batman38102, Requisite0, Sakindia123, TeamRegular and many others) and followed the Cyanogenmod guidelines to build a CWm recovery...
And I built a 6.0.2.8 (tuned to Cyanogenmod 10.0) with a working Kernel, a simple ramdisk, and so on...
...But I didn't test it yet...
...I'm still waiting due to my lack of a full firmware archive...
I also tried - for fun - to build the CWM 6.0.4.5 for Cyanogenmod 11.0 (beware: just a Blind Shot)
...using the 10.0 Kernel... working kernel but wrong configuration: it lacks Selinux capabilities (Working on it right now)...
...using a ramdisk tuned to JellyBean...
...filesystem nor permissive neither enforced...
..etc...
All things which can lead to a disaster while testing...
So, please, hold on until I'll test it on my own phone...
...if everything will be fine I'll be really happy to share it for the community...
See you soon on this thread then...
...news scheduled on incoming new year...
Click to expand...
Click to collapse
Dude batman38102 is me I changes my username long time back. Also dudes I got my Galaxy star unbricked so Im back. Ill help in anyway I can
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
---------- Post added at 10:46 AM ---------- Previous post was at 10:42 AM ----------
Also can u please pm me the test recovery. Im willing to test in anyway i can.
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
Hmmm
Ironman38102 said:
Dude batman38102 is me I changes my username long time back. Also dudes I got my Galaxy star unbricked so Im back. Ill help in anyway I can
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
---------- Post added at 10:46 AM ---------- Previous post was at 10:42 AM ----------
Also can u please pm me the test recovery. Im willing to test in anyway i can.
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
Click to expand...
Click to collapse
Hey thats gr8 hope we will get cm now.:victory:
CWM 6.0.2.8 Up and Running!
News about CWM 6.0.2.8 from CyanogenMod 10.0 (Jellybean 4.1.2):
I don't have a Github account (I'm not a developer) so I'll post here exactly what I did to build and set "up and running" this ClockWorkMod Recovery!
First of all, in my Google Drive you'll find everything we are Talking about... the experimental device tree, the recovery Odin archive, tools, binaries, ...
On first build everything was fine but the LCD screen didn't light up...
...Recovery was running, anyway, but I could not see anything...
...I could, perhaps, control the phone from PC with "adb shell"!
Code:
[email protected]:~$ [b]adb shell[/b]
~ # [b]ls[/b]
cache init.rc sdcard1
data preload sys
default.prop proc system
dev res tmp
efs root ueventd.goldfish.rc
etc sbin ueventd.rc
fstab.sp8810 sd-ext ueventd.sp8810.rc
init sdcard
~ #
Recovery log recorded the problem:
Code:
...
failed to put fb0 info
...
It's a framebuffer problem and the solution is pretty known; I pasted it from TeamRegular repository and put inside BoardConfig.mk with related sources:
Code:
...
BOARD_CUSTOM_GRAPHICS := ../../../device/samsung/sp8810/recovery/graphics.c
...
Well done! Recovery 6.0.2.8 up and running
Now testing:
- I can mount/unmount and list all filesystems
- I can backup the current firmware
- I can format and restore the external second partition (I use it a lot):
Code:
Creating filesystem with parameters:
Size: 1034944512
Block size: 4096
Blocks per group: 32768
Inodes per group: 7904
Inode size: 256
Journal blocks: 3948
Label:
Blocks: 252672
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/63232 inodes and 8244/252672 blocks
...
Found new backup image: /sdcard/clockworkmod/backup/2013-12-26.17.17.06//sd-ext.ext4.tar
Restoring sd-ext...
...
Code:
~ # [b]ls -l /sd-ext/[/b]
drwxrwx--x 2 system system 4096 Dec 22 12:54 dalvik-cache
drwxrwx--x 2 system system 4096 Dec 22 12:54 data
drwx------ 2 root root 4096 Dec 17 10:14 lost+found
~ #
- I can restore the boot image (and recovery of course):
Code:
...
Checking MD5 sums...
boot.img: OK
...
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Restore complete!
- I can Install boot images inside zip files from sdcard:
Code:
-- Installing: /sdcard/update_boot.zip
Finding update package...
I:Update location: /sdcard/update_boot.zip
Opening update package...
Installing update...
########################
# Doc Modded #
# new boot image #
########################
Installing Boot...
script result was [ ]
Installation Completed!!!!
- I can install zip files from sideload:
Code:
Sideload started ...
Now send the package you want to apply
to the device with "adb sideload <filename>"...
sideload_service invoked
adbd exiting after successful sideload
E:listen on USB
E:userid is 2000
E:Event loop starting
Restarting adbd...
Finding update package...
I:Update location: /tmp/update.zip
Opening update package...
Installing update...
if you read this, you
own a relaxed recovery!
Cheers :)
~ #
- I can "wipe cache":
Code:
-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Cache wipe complete.
- I can "wipe data/factory reset" :
Code:
-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2172633088
Block size: 4096
Blocks per group: 32768
Inodes per group: 7808
Inode size: 256
Journal blocks: 8287
Label:
Blocks: 530428
Block groups: 17
Reserved block group size: 135
Created filesystem with 11/132736 inodes and 17442/530428 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
...
Data wipe complete.
/tmp #
Notice: Actually this "CWM build" deals with /data encryption so ther is no need to apply any patch after factory reset
I took an extra-check with the following 'shell command' before and after the wipe action:
Code:
/ # [b]tune2fs -l /dev/block/mmcblk0p25[/b]
...
looking for no relevant differences!
..after boot... everything fine!
- Last but not least:
- I fully restored the previously backupped firmware:
Code:
...
...
Restore complete!
Easy Play
What's Wrong in this recovery?
I Dont Know...
Wish List?
Sure: I cannot handle /efs partition via 'menu options'...
...and everybody knows how dangerous could be wander around it
Doc_cheilvenerdi.org said:
News about CWM 6.0.2.8 from CyanogenMod 10.0 (Jellybean 4.1.2):
I don't have a Github account (I'm not a developer) so I'll post here exactly what I did to build and set "up and running" this ClockWorkMod Recovery!
First of all, in my Google Drive you'll find everything we are Talking about... the experimental device tree, the recovery Odin archive, tools, binaries, ...
On first build everything was fine but the LCD screen didn't light up...
...Recovery was running, anyway, but I could not see anything...
...I could, perhaps, control the phone from PC with "adb shell"!
Code:
[email protected]:~$ [b]adb shell[/b]
~ # [b]ls[/b]
cache init.rc sdcard1
data preload sys
default.prop proc system
dev res tmp
efs root ueventd.goldfish.rc
etc sbin ueventd.rc
fstab.sp8810 sd-ext ueventd.sp8810.rc
init sdcard
~ #
Recovery log recorded the problem:
Code:
...
failed to put fb0 info
...
It's a framebuffer problem and the solution is pretty known; I pasted it from TeamRegular repository and put inside BoardConfig.mk with related sources:
Code:
...
BOARD_CUSTOM_GRAPHICS := ../../../device/samsung/sp8810/recovery/graphics.c
...
Well done! Recovery 6.0.2.8 up and running
Now testing:
- I can mount/unmount and list all filesystems
- I can backup the current firmware
- I can format and restore the external second partition (I use it a lot):
Code:
Creating filesystem with parameters:
Size: 1034944512
Block size: 4096
Blocks per group: 32768
Inodes per group: 7904
Inode size: 256
Journal blocks: 3948
Label:
Blocks: 252672
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/63232 inodes and 8244/252672 blocks
...
Found new backup image: /sdcard/clockworkmod/backup/2013-12-26.17.17.06//sd-ext.ext4.tar
Restoring sd-ext...
...
Code:
~ # [b]ls -l /sd-ext/[/b]
drwxrwx--x 2 system system 4096 Dec 22 12:54 dalvik-cache
drwxrwx--x 2 system system 4096 Dec 22 12:54 data
drwx------ 2 root root 4096 Dec 17 10:14 lost+found
~ #
- I can restore the boot image (and recovery of course):
Code:
...
Checking MD5 sums...
boot.img: OK
...
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Restore complete!
- I can Install boot images inside zip files from sdcard:
Code:
-- Installing: /sdcard/update_boot.zip
Finding update package...
I:Update location: /sdcard/update_boot.zip
Opening update package...
Installing update...
########################
# Doc Modded #
# new boot image #
########################
Installing Boot...
script result was [ ]
Installation Completed!!!!
- I can install zip files from sideload:
Code:
Sideload started ...
Now send the package you want to apply
to the device with "adb sideload <filename>"...
sideload_service invoked
adbd exiting after successful sideload
E:listen on USB
E:userid is 2000
E:Event loop starting
Restarting adbd...
Finding update package...
I:Update location: /tmp/update.zip
Opening update package...
Installing update...
if you read this, you
own a relaxed recovery!
Cheers :)
~ #
- I can "wipe cache":
Code:
-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Cache wipe complete.
- I can "wipe data/factory reset" :
Code:
-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2172633088
Block size: 4096
Blocks per group: 32768
Inodes per group: 7808
Inode size: 256
Journal blocks: 8287
Label:
Blocks: 530428
Block groups: 17
Reserved block group size: 135
Created filesystem with 11/132736 inodes and 17442/530428 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
...
Data wipe complete.
/tmp #
Notice: Actually this "CWM build" deals with /data encryption so ther is no need to apply any patch after factory reset
I took an extra-check with the following 'shell command' before and after the wipe action:
Code:
/ # [b]tune2fs -l /dev/block/mmcblk0p25[/b]
...
looking for no relevant differences!
..after boot... everything fine!
- Last but not least:
- I fully restored the previously backupped firmware:
Code:
...
...
Restore complete!
Easy Play
What's Wrong in this recovery?
I Dont Know...
Wish List?
Sure: I cannot handle /efs partition via 'menu options'...
...and everybody knows how dangerous could be wander around it
Click to expand...
Click to collapse
Will dis wrk on s5282...??
Pls say Yes...
Yup u can use it
Sent from my GT-S5282 using Tapatalk
thanks
:good:
Doc_cheilvenerdi.org said:
News about CWM 6.0.2.8 from CyanogenMod 10.0 (Jellybean 4.1.2):
I don't have a Github account (I'm not a developer) so I'll post here exactly what I did to build and set "up and running" this ClockWorkMod Recovery!
First of all, in my Google Drive you'll find everything we are Talking about... the experimental device tree, the recovery Odin archive, tools, binaries, ...
On first build everything was fine but the LCD screen didn't light up...
...Recovery was running, anyway, but I could not see anything...
...I could, perhaps, control the phone from PC with "adb shell"!
Code:
[email protected]:~$ [b]adb shell[/b]
~ # [b]ls[/b]
cache init.rc sdcard1
data preload sys
default.prop proc system
dev res tmp
efs root ueventd.goldfish.rc
etc sbin ueventd.rc
fstab.sp8810 sd-ext ueventd.sp8810.rc
init sdcard
~ #
Recovery log recorded the problem:
Code:
...
failed to put fb0 info
...
It's a framebuffer problem and the solution is pretty known; I pasted it from TeamRegular repository and put inside BoardConfig.mk with related sources:
Code:
...
BOARD_CUSTOM_GRAPHICS := ../../../device/samsung/sp8810/recovery/graphics.c
...
Well done! Recovery 6.0.2.8 up and running
Now testing:
- I can mount/unmount and list all filesystems
- I can backup the current firmware
- I can format and restore the external second partition (I use it a lot):
Code:
Creating filesystem with parameters:
Size: 1034944512
Block size: 4096
Blocks per group: 32768
Inodes per group: 7904
Inode size: 256
Journal blocks: 3948
Label:
Blocks: 252672
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/63232 inodes and 8244/252672 blocks
...
Found new backup image: /sdcard/clockworkmod/backup/2013-12-26.17.17.06//sd-ext.ext4.tar
Restoring sd-ext...
...
Code:
~ # [b]ls -l /sd-ext/[/b]
drwxrwx--x 2 system system 4096 Dec 22 12:54 dalvik-cache
drwxrwx--x 2 system system 4096 Dec 22 12:54 data
drwx------ 2 root root 4096 Dec 17 10:14 lost+found
~ #
- I can restore the boot image (and recovery of course):
Code:
...
Checking MD5 sums...
boot.img: OK
...
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Restore complete!
- I can Install boot images inside zip files from sdcard:
Code:
-- Installing: /sdcard/update_boot.zip
Finding update package...
I:Update location: /sdcard/update_boot.zip
Opening update package...
Installing update...
########################
# Doc Modded #
# new boot image #
########################
Installing Boot...
script result was [ ]
Installation Completed!!!!
- I can install zip files from sideload:
Code:
Sideload started ...
Now send the package you want to apply
to the device with "adb sideload <filename>"...
sideload_service invoked
adbd exiting after successful sideload
E:listen on USB
E:userid is 2000
E:Event loop starting
Restarting adbd...
Finding update package...
I:Update location: /tmp/update.zip
Opening update package...
Installing update...
if you read this, you
own a relaxed recovery!
Cheers :)
~ #
- I can "wipe cache":
Code:
-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Cache wipe complete.
- I can "wipe data/factory reset" :
Code:
-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2172633088
Block size: 4096
Blocks per group: 32768
Inodes per group: 7808
Inode size: 256
Journal blocks: 8287
Label:
Blocks: 530428
Block groups: 17
Reserved block group size: 135
Created filesystem with 11/132736 inodes and 17442/530428 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
...
Data wipe complete.
/tmp #
Notice: Actually this "CWM build" deals with /data encryption so ther is no need to apply any patch after factory reset
I took an extra-check with the following 'shell command' before and after the wipe action:
Code:
/ # [b]tune2fs -l /dev/block/mmcblk0p25[/b]
...
looking for no relevant differences!
..after boot... everything fine!
- Last but not least:
- I fully restored the previously backupped firmware:
Code:
...
...
Restore complete!
Easy Play
What's Wrong in this recovery?
I Dont Know...
Wish List?
Sure: I cannot handle /efs partition via 'menu options'...
...and everybody knows how dangerous could be wander around it
Click to expand...
Click to collapse
---------- Post added at 12:12 PM ---------- Previous post was at 12:09 PM ----------
after cwm recovery 6 when cm 10.1 will release
Here is the screenshot. Check it out. Its tested by me on my s5282.
Here is screenshots. Tested by me on my s5282. I have also tested geatures like wipe data and back up rom ans flash zip from sd card and its working perfecly. Sure you should go for it
Sent from my GT-S5282 using Tapatalk
rahulsinghal said:
Here is screenshots. Tested by me on my s5282. I have also tested geatures like wipe data and back up rom ans flash zip from sd card and its working perfecly. Sure you should go for it
Sent from my GT-S5282 using Tapatalk
Click to expand...
Click to collapse
GR8...Congratulations....now we can expect a cm rom for our star.....
I know you guys must be counting on me for compiling. But I cant untill u guys setup a working device tree and kernel. Also my pc cant compile cm as I have a pc with very low spec. Sorry
Although I will still try but I cant promise anything since I have never worked on a device like this. Spreadtrum cpus are pretty much hard to hack.
also dudes I know how much your excited but we need to keep all development threads on topic!
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
Doc_cheilvenerdi.org said:
News about CWM 6.0.2.8 from CyanogenMod 10.0 (Jellybean 4.1.2):
I don't have a Github account (I'm not a developer) so I'll post here exactly what I did to build and set "up and running" this ClockWorkMod Recovery!
First of all, in my Google Drive you'll find everything we are Talking about... the experimental device tree, the recovery Odin archive, tools, binaries, ...
On first build everything was fine but the LCD screen didn't light up...
...Recovery was running, anyway, but I could not see anything...
...I could, perhaps, control the phone from PC with "adb shell"!
Code:
[email protected]:~$ [b]adb shell[/b]
~ # [b]ls[/b]
cache init.rc sdcard1
data preload sys
default.prop proc system
dev res tmp
efs root ueventd.goldfish.rc
etc sbin ueventd.rc
fstab.sp8810 sd-ext ueventd.sp8810.rc
init sdcard
~ #
Recovery log recorded the problem:
Code:
...
failed to put fb0 info
...
It's a framebuffer problem and the solution is pretty known; I pasted it from TeamRegular repository and put inside BoardConfig.mk with related sources:
Code:
...
BOARD_CUSTOM_GRAPHICS := ../../../device/samsung/sp8810/recovery/graphics.c
...
Well done! Recovery 6.0.2.8 up and running
Now testing:
- I can mount/unmount and list all filesystems
- I can backup the current firmware
- I can format and restore the external second partition (I use it a lot):
Code:
Creating filesystem with parameters:
Size: 1034944512
Block size: 4096
Blocks per group: 32768
Inodes per group: 7904
Inode size: 256
Journal blocks: 3948
Label:
Blocks: 252672
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/63232 inodes and 8244/252672 blocks
...
Found new backup image: /sdcard/clockworkmod/backup/2013-12-26.17.17.06//sd-ext.ext4.tar
Restoring sd-ext...
...
Code:
~ # [b]ls -l /sd-ext/[/b]
drwxrwx--x 2 system system 4096 Dec 22 12:54 dalvik-cache
drwxrwx--x 2 system system 4096 Dec 22 12:54 data
drwx------ 2 root root 4096 Dec 17 10:14 lost+found
~ #
- I can restore the boot image (and recovery of course):
Code:
...
Checking MD5 sums...
boot.img: OK
...
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Restore complete!
- I can Install boot images inside zip files from sdcard:
Code:
-- Installing: /sdcard/update_boot.zip
Finding update package...
I:Update location: /sdcard/update_boot.zip
Opening update package...
Installing update...
########################
# Doc Modded #
# new boot image #
########################
Installing Boot...
script result was [ ]
Installation Completed!!!!
- I can install zip files from sideload:
Code:
Sideload started ...
Now send the package you want to apply
to the device with "adb sideload <filename>"...
sideload_service invoked
adbd exiting after successful sideload
E:listen on USB
E:userid is 2000
E:Event loop starting
Restarting adbd...
Finding update package...
I:Update location: /tmp/update.zip
Opening update package...
Installing update...
if you read this, you
own a relaxed recovery!
Cheers :)
~ #
- I can "wipe cache":
Code:
-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Cache wipe complete.
- I can "wipe data/factory reset" :
Code:
-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2172633088
Block size: 4096
Blocks per group: 32768
Inodes per group: 7808
Inode size: 256
Journal blocks: 8287
Label:
Blocks: 530428
Block groups: 17
Reserved block group size: 135
Created filesystem with 11/132736 inodes and 17442/530428 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
...
Data wipe complete.
/tmp #
Notice: Actually this "CWM build" deals with /data encryption so ther is no need to apply any patch after factory reset
I took an extra-check with the following 'shell command' before and after the wipe action:
Code:
/ # [b]tune2fs -l /dev/block/mmcblk0p25[/b]
...
looking for no relevant differences!
..after boot... everything fine!
- Last but not least:
- I fully restored the previously backupped firmware:
Code:
...
...
Restore complete!
Easy Play
What's Wrong in this recovery?
I Dont Know...
Wish List?
Sure: I cannot handle /efs partition via 'menu options'...
...and everybody knows how dangerous could be wander around it
Click to expand...
Click to collapse
Lol i have uploaded all those codes to github. http://github.com/batman38102/android_device_samsung_mint
My phone is rooted using Kingoroot its was all running smooth until i update my phone now its stuck on boot logo i really need SWIPE KONNCET PLUS STOCK FIRMWARE Please help me please :crying: :crying:
Zaroonok said:
My phone is rooted using Kingoroot its was all running smooth until i update my phone now its stuck on boot logo i really need SWIPE KONNCET PLUS STOCK FIRMWARE Please help me please :crying: :crying:
Click to expand...
Click to collapse
What android version where you at and what did it upgrade to? Also, try booting into recovery and erasing all data.
i had tried everything i had wipe cache it and hard reset it too but still nothing work for me i just need a stock firmware of that mobile (Mobile name is swipe konnect plus ) and my phone android version is 5.1 lollipop please help me :crying:
what recovery is installed?
Need stock rom and custom recovery
Hey pls give me swipe konnect plus stock rom and custom recovery
aksthecount said:
Hey pls give me swipe konnect plus stock rom and custom recovery
Click to expand...
Click to collapse
That is unfortunately not how it works here...
swipe konnect plus error on inatalling cm12.1
I port a cm 12.1 for swipe konnect plus mt6580 when I flash cm with twrp 3.0.1 I am getting error like this.
Installing zip file '/sdcard/files/CyanoGenMod 12.1.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
/file_contexts: line 262 has invalid file type ubject_r:wmtWifi_device:s0/cache/dalvik-cache(/.*)?
|========================|
| CM12.1 r36 March BUILD |
| For Micromax A106 |
| BY MANAN VALLECHA |
| ---thanks from heart-- |
|Vijay , Ranjan , Vivek |
|Source - Rohan Taneja |
|========================|
minzip: Extracted 3 file(s)
could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
unmount of /system failed; no such volume
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Creating filesystem with parameters:
Size: 262144
Block size: 4096
Blocks per group: 32768
Inodes per group: 16
Inode size: 256
Journal blocks: 1024
Label:
Transparent compression: none
Blocks: 64
Block groups: 1
Reserved block group size: 7
error: ext4_allocate_best_fit_partial: failed to allocate 973 blocks, out of space?
format: make_ext4fs failed (1) on /dev/block/mmcblk0p5could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
minzip: Extracted 1493 file(s)
ApplyParsedPerms: removexattr of /system/xposed.prop to 0 failed: Operation not supported on transport endpointscript aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard/files/CyanoGenMod 12.1.zip'
What to do pls help me pls........pls.......
aksthecount said:
I port a cm 12.1 for swipe konnect plus mt6580 when I flash cm with twrp 3.0.1 I am getting error like this.
Installing zip file '/sdcard/files/CyanoGenMod 12.1.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
/file_contexts: line 262 has invalid file type ubject_r:wmtWifi_device:s0/cache/dalvik-cache(/.*)?
|========================|
| CM12.1 r36 March BUILD |
| For Micromax A106 |
| BY MANAN VALLECHA |
| ---thanks from heart-- |
|Vijay , Ranjan , Vivek |
|Source - Rohan Taneja |
|========================|
minzip: Extracted 3 file(s)
could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
unmount of /system failed; no such volume
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Creating filesystem with parameters:
Size: 262144
Block size: 4096
Blocks per group: 32768
Inodes per group: 16
Inode size: 256
Journal blocks: 1024
Label:
Transparent compression: none
Blocks: 64
Block groups: 1
Reserved block group size: 7
error: ext4_allocate_best_fit_partial: failed to allocate 973 blocks, out of space?
format: make_ext4fs failed (1) on /dev/block/mmcblk0p5could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
minzip: Extracted 1493 file(s)
ApplyParsedPerms: removexattr of /system/xposed.prop to 0 failed: Operation not supported on transport endpointscript aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard/files/CyanoGenMod 12.1.zip'
What to do pls help me pls........pls.......
Click to expand...
Click to collapse
What'd you use to port the ROM? Android kitchen or yourself? What kernel do you use?
I port it myself with XDA guide
I use custom ROM kernal 3.4.x and copy my kernal file uevent.tc and zimage file my kernal very is 3.10.72+
---------- Post added at 03:56 PM ---------- Previous post was at 03:53 PM ----------
It says unable to mount dev/block/mmcblk05/at system
---------- Post added at 04:01 PM ---------- Previous post was at 03:56 PM ----------
What does that mean
Hey, RAZERDAHACKER pls hlp me pls,pls,.......
Stock firmware for swipe konnect plus
aksthecount said:
Hey pls give me swipe konnect plus stock rom and custom recovery
Click to expand...
Click to collapse
Hello , if you really want the stock firmware then reply of this message . I will tell you where you can find the STOCK firmware for this device. But for sharing link of another Website i need permission from this XDA team. If they allow me then i can post here the link of the STOCK firmware.
Thank you .. and waiting for your reply.
sorry for late mess yaa give me the link
aksthecount said:
sorry for late mess yaa give me the link
Click to expand...
Click to collapse
tap on the quoted thread below to view the full answer
x.ak**** said:
like all my comments above to encourage me to help you.
Okay so first of all i will let you know why a phone gets bricked-
>corrupted rom
>some system files got deleted
>rooting
>modding
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
my case
i always keep two phones with me like one for my experiments and one as a backup. In this case i'll be talking about my lyf wind 3 that got bricked.
>actually i was trying to install twrp onto that phone but first i had to root it, and due to the upgraded android security, i wasn't able to do via kingoroot so i tried i-root and it did the job but instead of kingo-superuser i got some ****ty superuser so i tried granting permission to the actual superuser and while doing so i accidentally double rooted my phone (first with i-root and then with kingoroot), which was kinda stupid, so it just deleted some system files and my phone wouldn't boot after that. It just got stuck on the boot logo.
Click to expand...
Click to collapse
x.ak**** said:
tap on the quoted thread below to view the full answer
Click to expand...
Click to collapse
My case was that I flash cm 12 on my swipe konnect plus n was working fine but was reddish the common bug of cyanogenmod
and it can be fixed no matter how many I change file to clear bug so I just lost hope then I restore my stock via twrp n then the mobile was lagging to much so then I thought that it must be coz that twrp didn't restore my stock properly so search on Google swipe konnect plus firmware n I got the site on firmwarefile.com there was three stock room for swipe konnect plus so I download all of them n when I flash one of them it got brick then I flash another but sp flash tool giving me error "dram enable failed"
So I googled it n found that if we flash wrong preloader it hard brick your device that means the firmware for swipe konnect plus on the website r all wrong firmware n also check the build.prop of it was written the same model but I don't know what is happening I just want to abuse whoever upload swipe konnect plus firmware coz it brick my device pls if anyone is reading this pls pls pls pls help me to I just want preloader.bin file for my device if anyone anyone or your frnd is using swipe konnect plus pls pls pls pls contact me on my email [email protected]
---------- Post added at 09:29 PM ---------- Previous post was at 09:21 PM ----------
Zaroonok said:
My phone is rooted using Kingoroot its was all running smooth until i update my phone now its stuck on boot logo i really need SWIPE KONNCET PLUS STOCK FIRMWARE Please help me please :crying: :crying:
Click to expand...
Click to collapse
Hey do u still have swipe konnect plus reply me pls
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my version for the Samsung Galaxy Note 2 LTE on LineageOS 18.1.
At first I want to thank @rINanDO, @ChronoMonochrome for all your work which was reused here and helped a lot.
This ROM is only tested with N7105, so maybe you could to give me a feedback if it does or does not work with all the different Note 2 LTE variants.
It theoretically should fit for:
SGH-I317
SGH-I317M
SCH-I605
SPH-L900
SGH-T889
SHV-E250S
SHV-E250K
SHV-E250L
SC-02E
GT-N7105/N7105T
SGH-T889V
SHV-E250S/E250K/E250L
SC-02E (SGH-N025)
Here you can see how far everything is working:
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
Wifi
USB
Video playback (HW/SW)
OTA Updates
RIL
GPS
Tethering via USB, WIFI and Bluetooth
Sensors, except compass
Spoiler: Whats not working
Maybe random reboots because of a modem crash
Maybe more
Spoiler: Links
TWRP
ROM
Spoiler: If you're facing installation problems.
Samsung seems to use differen't partition tables for these devices,
so far we know a t889, I317 and maybe other devices != n7105 are having a too small HIDDEN (for us vendor) partition.
So if you're facing problems like here
Getting "E2001: Failed to update vendor image." during clean flash.
This means that you have to resize it, check out these two posts:
Manual way
Zip way
If you are going to use Gapps,
I recommend to use the pico package!
https://opengapps.org/
For the others, you can use microG if you want, I've enabled signature spoofing.
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: Changelog
26.10.2021
31.10.2021
09.11.2021
09.12.2021
07.01.2022
19.01.2022
28.02.2022
20.04.2022
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][11.x][N7105/T0LTE][BETA] LineageOS 18.1, ROM for the Samsung Galaxy Note 2 LTE
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 11.x R
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.3.0
Based On: LineageOS
Version Information
Status: Beta
SELINUX: permissive
Created 2021-10-11
Last Updated 2022-04-20
If you're interested in flashing your first GSI, follow this thread (also alpha, untested till yet):
[GSI][11][ EXYNOS4 SMDK4412 ][N8000, N801X, N8020, I9300, N5100, N51XX, N7100, ...][ALPHA] [EOL]
Here you will find my exynos4 compatible GSI's. This work is based on the magic of @phhusson, so thank you very much for this. Don't forget, that you need an treblelized ROM to support this. Do you like my work? Than you can simply hit...
forum.xda-developers.com
thanks for this.
Getting "E2001: Failed to update vendor image." during clean flash.
Your LineageOS 16.0 builds work fine. Probably related to Project Treble?
Device: SGH-T889
TWRP: 3.5.2_9-1
samsungnote2xda said:
Your LineageOS 16.0 builds work fine. Probably related to Project Treble?
Click to expand...
Click to collapse
Hmm the problem could be, that maybe the T889 has a different partition size. Could you send me the complete recovery log?
html6405 said:
Hmm the problem could be, that maybe the T889 has a different partition size. Could you send me the complete recovery log?
Click to expand...
Click to collapse
here you go
samsungnote2xda said:
here you go
Click to expand...
Click to collapse
I can't see any log file .
html6405 said:
I can't see any log file .
Click to expand...
Click to collapse
my bad can't attach file.
https://ghostbin.com/1PdoR/raw
samsungnote2xda said:
my bad can't attach file.
https://ghostbin.com/1PdoR/raw
Click to expand...
Click to collapse
Ok... try to format the vendor partition before as ext4, then retry to install the zip file.
html6405 said:
Ok... try to format the vendor partition before as ext4, then retry to install the zip file.
Click to expand...
Click to collapse
same issue. formatted partition using make_ext4fs
samsungnote2xda said:
same issue. formatted partition using make_ext4fs
Click to expand...
Click to collapse
Ok, than please send me the output from:
adb shell
su
blockdev --getsize64 /dev/block/platform/dw_mmc/by-name/HIDDEN
html6405 said:
Ok, than please send me the output from:
adb shell
su
blockdev --getsize64 /dev/block/platform/dw_mmc/by-name/HIDDEN
Click to expand...
Click to collapse
~ # blockdev --getsize64 /dev/block/platform/dw_mmc/by-name/HIDDEN
20971520
samsungnote2xda said:
~ # blockdev --getsize64 /dev/block/platform/dw_mmc/by-name/HIDDEN
20971520
Click to expand...
Click to collapse
Thx, I will check this and create a new version.
html6405 said:
Thx, I will check this and create a new version.
Click to expand...
Click to collapse
I'm sorry, but the partition size is too small on your device :/,
on a n7105 the partition size is 587202560.
This means, that you would have to re-partition your device with parted and expand vendor (in the same switch you could expand system up to 2GB).
Or the last thing would be, that I'm building a not treblelized ROM for these devices, but this would be again much work.
html6405 said:
I'm sorry, but the partition size is too small on your device :/,
on a n7105 the partition size is 587202560.
This means, that you would have to re-partition your device with parted and expand vendor (in the same switch you could expand system up to 2GB).
Or the last thing would be, that I'm building a not treblelized ROM for these devices, but this would be again much work.
Click to expand...
Click to collapse
ok so reassign space from /cache?
/cache | /dev/block/platform/dw_mmc/by-name/CACHE | Size: 1259MB Used: 21MB Free: 1237MB Backup Size: 21MB
samsungnote2xda said:
ok so reassign space from /cache?
Click to expand...
Click to collapse
I would make the data partition a little bit smaller.
I couldn't got through google setup, so I flashed only LOS. It's mostly working.
Trust issued 2 warnings: not in restricted mode, and "signed with public key".
Like in other devices there is a problem with quick access settings - blinking when press and hold (occured after reboot). In Note 3 it took some time before resolved.
SIM works, Wi-fi works not sure about GPS. I have 7105 model.
And one more - in update menu can't tick "update lineage recovery", which I dont use.
I tried OGapps pico latest.
Anyway it's a miracle You almost made it brillant .
Many thanks.
P.S.
Switching off icons descriptions solve q.access problem.
html6405 said:
I would make the data partition a little bit smaller.
Click to expand...
Click to collapse
thanks. it worked.
Spoiler: parted
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB fat16 RADIO
11 164MB 432MB 268MB ext4 TOMBSTONES
12 432MB 1432MB 1000MB ext4 CACHE
13 1432MB 3432MB 2000MB ext2 SYSTEM
14 3432MB 4200MB 768MB ext4 HIDDEN
15 4200MB 4208MB 8000kB OTA
16 4208MB 15.8GB 11.5GB ext4 USERDATA
No3te said:
I couldn't got through google setup, so I flashed only LOS. It's mostly working.
Click to expand...
Click to collapse
OK, I had no problem with this, what happened?
No3te said:
Trust issued 2 warnings: not in restricted mode, and "signed with public key".
Click to expand...
Click to collapse
This is normal, because selinux is permissive.
No3te said:
And one more - in update menu can't tick "update lineage recovery", which I dont use.
Click to expand...
Click to collapse
Ah you're right, I will remove or disable this, because I've removed the lineage recovery from the build in general,
I don't wan't that TWRP will be overwritten...
No3te said:
Like in other devices there is a problem with quick access settings - blinking when press and hold (occured after reboot). In Note 3 it took some time before resolved.
Click to expand...
Click to collapse
I'm unsure what do you mean with this
html6405 said:
OK, I had no problem with this, what happened?
This is normal, because selinux is permissive.
Ah you're right, I will remove or disable this, because I've removed the lineage recovery from the build in general,
I don't wan't that TWRP will be overwritten...
I'm unsure what do you mean with this
Click to expand...
Click to collapse
After choosing language in initial set up, it says - google voice services not working, 2 more set up screens and it stops in "wait a minute" screen.
Voice service not working in AOSP keyboard.
Another problem is well known in Note 3 ROMS - 10 and 11.
When you pull qa menu from the top of screen you get icons: wifi, battery etc. While pressing and holding battery icon(and some others) screen blinks to black, says "interface crashed" and goes back to normal.
"Solution" to this is switch off description under icons.
Sorry for not giving "logs" but it's over my skills.
Tried to send "bug report" but it warns about privacy ...
I will try Mind the gapps, what helped me with Note 3.
No3te said:
After choosing language in initial set up, it says - google voice services not working, 2 more set up screens and it stops in "wait a minute" screen.
Voice service not working in AOSP keyboard.
Click to expand...
Click to collapse
Hmm ok, I didn't test google voice service...
No3te said:
Another problem is well known in Note 3 ROMS - 10 and 11.
When you pull qa menu from the top of screen you get icons: wifi, battery etc. While pressing and holding battery icon(and some others) screen blinks to black, says "interface crashed" and goes back to normal.
Click to expand...
Click to collapse
Hmm, strange, this seems to work with my device.