This is the latest ROM for P7500 available on sammobiles (Czech version) with the deepsleep / wakelock / battery drain issue fixed.
{
"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"
}
Download link at the bottom of this post.
It's actually a mashup of two roms: P7500XWMPJ_P7500XEZMP1_XEZ (Czech) and P7500ZCLP9_P7500OZHLP9_CHN (China). See below for details.
Background
Since the ICS update, the P7500 tab drains the battery much faster than previous honeycomb versions. It is commonly accepted that this behavior is due to a bug in the kernel that prevents the CPU from deep sleeping. You can verify how much the tab spends in each CPU mode with the CpuSpy app.
How this was fixed
Stiffmeister, a member of a german forum (page 30 onwards) found out that the CHN firmware does NOT have this bug. Massive credit goes to him. His solution involves flashing the CHN firmware, then CWM recovery, then a CWM update that adds additional languages. It remains unknown why the Chinese ROM fixes the deepsleep issues, but so far it's the only one that does.
Phibs, a XDA member further found out that the problem can also be fixed by flashing the boot.img + kernel modules + wpa_supplicant from the chinese rom. It is explained here and there is even a zip file you can flash from CWM on top of an ICS stock rom. Massive credit to him, too.
About this ROM
This is essentally the latest ROM from sammobile (XWMPJ - Czech) with the following modifications:
Replaced boot.img with CHN's
Replaced /system/lib/modules/* with CHN's
Replaced /system/bin/wpa_supplicant with CHN's
Removed recovery.img to prevent overwrite of existing recovery.
No changes have been made other than these.
Flashing with odin won't destroy your current recovery nor your data so it's safe to flash on top of an existing stock ICS. Nandroid first if it feels safer. Wipe not needed if coming from stock ICS. Flashing on top of honeycomb not tested.
Root
This is a non-root rom. You can root it yourself if you want. Your options are:
Flash this
or use the XWMPJ ROM from Toldo's thread, bonus packed with deodex, zipalign, init.d and root.
Flash
As stated elsewhere in this post and throughout the thread, flash with Odin.
How to cook your own
If you want to use another (non-Czech) rom as a base and patch it with the china boot.img yourself, follow this procedure:
Grab the two roms (CHN and the one you want to patch) from sammobile.
Grab ext4_utils from here.
Go to linux
Unzip ext4_utils and make them:
Code:
make
Untar the roms in two separate folders (I used cn for china, cz for czech)
On cn and cz, use simg2img from ext4_utils to turn system.img into an ext4 raw file:
Code:
./simg2img cn/system.img cn/system.ext4
./simg2img cz/system.img cz/system.ext4
Mount both cn and cz images:
Code:
mkdir cn/fs
mkdir cz/fs
sudo mount -o loop cn/system.ext4 cn/fs
sudo mount -o loop cz/system.ext4 cz/fs
We will be replacing cz's kernel with cn's later, these are dependent files that need to be copied over from cn to cz:
Code:
sudo cp cn/fs/lib/modules/* cz/fs/lib/modules
sudo cp cn/fs/bin/wpa_supplicant cz/fs/bin/wpa_supplicant
sudo cp cn/fs/bin/wlandutservice cz/fs/bin/wlandutservice
Now, find out what the block size and count were in the original img. Size * count / (1024 * 1024) will give you the filesystem size in MB, we will use it in the next step.
Code:
tune2fs -l cz/system.ext4
Rebuild the android image with make_ext4fs (from ext4_utils). 578M is the size in MB, and 4096 is the block size from the above step:
Code:
rm cz/system.img
sudo ./make_ext4fs -s -l 578M -b 4096 -a system cz/system.img cz/fs
You can unmount and remove temporary stuff now:
Code:
umount cn/fs
umount cz/fs
rmdir cn/fs cz/fs
rm cz/system.ext4
Copy boot.img over from cn to cz:
Code:
cp cn/boot.img cz/boot.img
If you have a custom recovery such as CWM and don't want it to be destroyed by odin when flashing this, remove cz/recovery.img:
Code:
rm cz/recovery.img
Now, Odin needs all the img files packed into a tar file with a md5 checksum piggybacked at the end:
Code:
cd cz
tar -H ustar -c *.bin *.img > rom.tar
md5sum rom.tar >>rom.tar
mv rom.tar rom.tar.md5
That's it, go to Odin and flash rom.tar.md5. Do not rename "rom.tar.md5" or Odin will complain. If you want to give it a more meaningful name (for distribution or whatever), rename "rom.tar" before piggybacking the md5.
Download
P7500XWMPJ_deepsleep.7z (350.2 MB)
@ mega: https://mega.co.nz/#!BxU1iC6Y!Paaqp1C1KevBRA9caSAGVy-4ynwOxdxf2hWogk49nEg
@ hotfile: https://hotfile.com/dl/202781788/50a705c/P7500XWMPJ_deepsleep.7z.html
Odin tells this
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> P7500XWMPJ_deepsleep.tar.md5 is invalid.
<OSM> End...
when I try to flash your Rom
Thanks!
My only question is if I want to flash CM10, flashing this ROM with Odin before will fix the deepsleep in CM10?
S_Hammer said:
Odin tells this
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> P7500XWMPJ_deepsleep.tar.md5 is invalid.
<OSM> End...
when I try to flash your Rom
Click to expand...
Click to collapse
His ROM is not odin flash, you need to flash the zip it in recovery.
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 06:34 AM ---------- Previous post was at 06:30 AM ----------
LluisAzm said:
Thanks!
My only question is if I want to flash CM10, flashing this ROM with Odin before will fix the deepsleep in CM10?
Click to expand...
Click to collapse
This ROM is not for Odin.
No it won't, when u flash cm10 it will replace the files. This only for flashing over the ROM.
You can't replace these files in cm10 it won't fix the problem, this only works for stock ROMs.
For cm10 try KK2 radio with latest nightly, been working great for me for over two days now, 0.6% loss per hour
Sent from my Nexus 4 using xda app-developers app
LluisAzm said:
My only question is if I want to flash CM10, flashing this ROM with Odin before will fix the deepsleep in CM10?
Click to expand...
Click to collapse
No, CM10 will overwrite the chinese kernel which fixes the bug.
S_Hammer said:
<OSM> MD5 hash value is invalid
<OSM> P7500XWMPJ_deepsleep.tar.md5 is invalid.
Click to expand...
Click to collapse
Fixed. The md5 didn't match the actual tar name...
I've updated the link, you can redownload.
... or just rename the file to "rom.tar.md5" and odin should be okay with it.
javideslomao said:
No, CM10 will overwrite the chinese kernel which fixes the bug.
Click to expand...
Click to collapse
Check http://live.samsung-updates.com/index.php?device=GT-P7500
Often besides full firmware, also the separate Kernel can be downloaded (often, not always). So you can combine your regional firmware with specific kernel (flashable via (mobile) odin)), like XWMPE, F, I, J, whatever.
Dead Silence said:
Often besides full firmware, also the separate Kernel can be downloaded (often, not always). So you can combine your regional firmware with specific kernel (flashable via (mobile) odin)), like XWMPE, F, I, J, whatever.
Click to expand...
Click to collapse
The problem is that the wireless module (dhd.ko) lives in /system (ie. not included in boot.img), so if the kernel has a different ABI, the modules must be updated for the wifi to work. Or, at least, that's what happens when merging czech + china.
tested on my tab for 5 days. it's true - sleeps like a baby.
40 % batery lost ofter 5 dayes
nice
is it a dream?
no i am awake!!!!
Could someone please mirror the ROM? Mega is really sucks!!! The download speed is 10 Kb/s instead of 370 Kb/s!!!
soroush0313 said:
Could someone please mirror the ROM? Mega is really sucks!!! The download speed is 10 Kb/s instead of 370 Kb/s!!!
Click to expand...
Click to collapse
You may try this, instead of installing a full rom.
Install CWM and then install the zip file.
http://forum.xda-developers.com/showthread.php?t=2164447&page=3
odeccacccp said:
This ROM is not for Odin.
No it won't, when u flash cm10 it will replace the files. This only for flashing over the ROM.
You can't replace these files in cm10 it won't fix the problem, this only works for stock ROMs.
For cm10 try KK2 radio with latest nightly, been working great for me for over two days now, 0.6% loss per hour
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Where could I find the KK2 radio to try it if it might work?
Phibs said:
You may try this, instead of installing a full rom.
Install CWM and then install the zip file.
http://forum.xda-developers.com/showthread.php?t=2164447&page=3
Click to expand...
Click to collapse
This does not work, i get "recovery bootloop". This is also confirmed in Toldo's thread: http://forum.xda-developers.com/showthread.php?t=1813651&page=131
Perfect Rom. Deep sleep working properly.
Thanx.
so, how do i install the rom? is by odin or cwm?
is it odex or de-odex?
thanks.
Hmm strange, I wanted to try this rom and I was on CM 10.1. I did go to recovery wipe system, data, cache and dalvik and now there is nothing on my internal storage and I can't see the rom in order to flash it
How is this possible?
Hello, I have flashed the ROM but i can't root it... I flash cwm and Samsung_Galaxy_Tab_10.1_root.zip but doesn't work...
Anyone have root it?
Thanks!
LluisAzm said:
Hello, I have flashed the ROM but i can't root it... I flash cwm and Samsung_Galaxy_Tab_10.1_root.zip but doesn't work...
Anyone have root it?
Thanks!
Click to expand...
Click to collapse
Worked for me.
cnn888 said:
so, how do i install the rom? is by odin or cwm?
is it odex or de-odex?
thanks.
Click to expand...
Click to collapse
Via Odin, read the OP. And ist pure Stock, means odexed.
Vertumus said:
Hmm strange, I wanted to try this rom and I was on CM 10.1. I did go to recovery wipe system, data, cache and dalvik and now there is nothing on my internal storage and I can't see the rom in order to flash it
How is this possible?
Click to expand...
Click to collapse
Its not a ROM, ist a firmware. So flash it via odin.
Related
Re-released flashable zip version for those people who are stuck at Froyo because of modem issues
Features:
Modified CWM to support Froyo. Credits to tj_style for porting CWM on Galaxy Mini ==> http://forum.xda-developers.com/showthread.php?t=1167750
Uses tj_style's overclock kernel ==> http://forum.xda-developers.com/showpost.php?p=12880870&postcount=39
All partitions @ Ext4
Pre-rooted
Deodex
Bootanimation
init.d support (running custom scripts during boot)
cifs and tun modules
Darktremor Apps2SD 2.7.5.3 Beta 03
Removed startup sound
Changed default language to English
Added some live wallpapers
TouchWiz replaced with zeam
Pre-installed apps: OpenVPNSettings (inlcuding binary), Screenoffandlock, and CifsManager
Others
FLASHING DISCLAIMER APPLIES!
Should anything go wrong, please make sure you have a backup of your firmware from samfirmware.com or use CheckFus http://forum.xda-developers.com/showthread.php?t=1032437
How to install from stock firmware:
This procedure assumes that you are still using Froyo so there is no need to flash any firmware
1. Download attached ClockworkMod (CWM) Recovery for Froyo. Flash as 'One Pacakge' using Odin
2. Download S5570XWKC1_MOD_ROM.zip and save it on the root your SD card ==> http://www.multiupload.com/0INURR5M72
3. Turn off phone. Go into recovery mode by pressing and holding the Home + Power buttons. Release buttons when you see the Samsung logo
4. Once you are in recovery mode you will get lot of options on screen. In recovery mode touchscreen does not work, so use the Volume button to toggle through options, Home button to select option or confirm action, and Power or Back button to go back to the previous menu.
5. Select 'wipe data / reset'. Confirm action
6. Select 'install zip from sd > 'choose zip from sdcard' > file in Step 2. Confirm action
7. Go back to previous menu and select 'reboot system now'
Done!
Stock theme
{
"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"
}
Quadrant (600MHz)
Quadrant (overclocked)
thanks for this rom really like it) i have just 1 tiny problem :-s when i press home and select task manager it force stops :| this is the only thing that bother me
I can't recreate your issue. Does it happen all the time or in just some cases?
Thank you Parasmi!!! You rock!!! Already downloading and I'll give it a try tomorrow!!!
does the dark font in menu exist in this release too?
if not i'm going to install it
trance89 said:
does the dark font in menu exist in this release too?
if not i'm going to install it
Click to expand...
Click to collapse
No because this is stock theme.
Please note this is a Froyo ROM. If you are coming from Gingerbread, you need to flash a Froyo firmware first using Odin.
parasmi said:
I can't recreate your issue. Does it happen all the time or in just some cases?
Click to expand...
Click to collapse
all the time. you know? when i press menu it pops up recent apps and under the task manager.when i press on task manager phone vibrates and i got the "force close " message.same if i press the task manager from menu :-?
Great work Parasmi.
It's just one thing that I will ask you to consider : some apps that you included in the zip package. For instance, AFAIK Root Explorer is only available as paid version only. How could you manage to include it in your ROM ? I hate to see this great ROM turned into a warez ROM. And secondly, SetCPU, though it's free for xda-dev members, its' developer explicitly asked ROM Developers not to include SetCPU. You can see his post here :
SetCPU for Root Users [2.2.4] Undervolting and more 07/07/2011
Or I'll just quote part of his OP here :
coolbho3000 said:
ROM developers: Please do not include SetCPU in your ROM. I appreciate the work you're doing, but link to this thread instead, and I'd really appreciate it if you mention that SetCPU is available on the Android Market.
SetCPU is a CPU speed tweaking application for Android. More specifically, it allows control of certain aspects of the Linux cpufreq driver, allowing for overclocking, underclocking, or tweaking speeds and settings on many Android devices. It will work with most if not all rooted Android 1.5/1.6/2.0/2.1/2.2/2.3/3.0/3.1 builds on most devices.
The program is free here for XDA members. It costs 1.99 on the Android Market and available for purchase on the Amazon Appstore for users in the US.
QR code (please donate by buying it on the market ):
Click to expand...
Click to collapse
Cheers
distan7 said:
Great work Parasmi.
It's just one thing that I will ask you to consider : some apps that you included in the zip package. For instance, AFAIK Root Explorer is only available as paid version only. How could you manage to include it in your ROM ? I hate to see this great ROM turned into a warez ROM. And secondly, SetCPU, though it's free for xda-dev members, its' developer explicitly asked ROM Developers not to include SetCPU. You can see his post here :
SetCPU for Root Users [2.2.4] Undervolting and more 07/07/2011
Or I'll just quote part of his OP here :
Cheers
Click to expand...
Click to collapse
Thank you for the reminder. I'm having seconds thought about them actually. I'll remove them and re-upload a new file
adistf said:
all the time. you know? when i press menu it pops up recent apps and under the task manager.when i press on task manager phone vibrates and i got the "force close " message.same if i press the task manager from menu :-?
Click to expand...
Click to collapse
Not happening to me. Try launching task manager via applications, let's see how it goes
I get E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
when I do wipe data / reset
after that I still go ahead and flash rom zip but it then says
E: Error in /sdcard/S5570XWKC1_MOD_ROM.zip (Status 0)
Installation aborted.
and if I reboot it's stuck at Galaxy mini screen
Any ideas?
I'll have to flash my backup
splattx_x said:
I get E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
when I do wipe data / reset
Click to expand...
Click to collapse
Does you SD have a 2nd partition?
after that I still go ahead and flash rom zip but it then says
E: Error in /sdcard/S5570XWKC1_MOD_ROM.zip (Status 0)
Installation aborted.
and if I reboot it's stuck at Galaxy mini screen
Any ideas?
I'll have to flash my backup
Click to expand...
Click to collapse
Im not sure abour this one. Can you check if the zip file is not corrupted?
parasmi said:
Does you SD have a 2nd partition?
Click to expand...
Click to collapse
No, I only have one partition in FAT format.
parasmi said:
Im not sure abour this one. Can you check if the zip file is not corrupted?
Click to expand...
Click to collapse
I tried once, failed. Then I deleted the file from SDcard, copied it again but it failed again with same error... I was able to extract the zip correctly so I don't think the file is corrupt. Perhaps Latin and European devices are more different than we thought.
splattx_x said:
No, I only have one partition in FAT format.
I tried once, failed. Then I deleted the file from SDcard, copied it again but it failed again with same error... I was able to extract the zip correctly so I don't think the file is corrupt. Perhaps Latin and European devices are more different than we thought.
Click to expand...
Click to collapse
Hhmmm....Let's take this offline. Sent you PM
Hi,
Does this ROM work with my phone?
PDA: S5570XWKC7
PHONE: S5570XXB1
CSC: S5570XXKC3
System information shows me exactly the same version number, except Build is FROYO.XWKC7 compared to FROYO.XWKC1
the same happen with me plz edit ur scrpit and thanks
splattx_x said:
I get E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
when I do wipe data / reset
after that I still go ahead and flash rom zip but it then says
E: Error in /sdcard/S5570XWKC1_MOD_ROM.zip (Status 0)
Installation aborted.
and if I reboot it's stuck at Galaxy mini screen
Any ideas?
I'll have to flash my backup
Click to expand...
Click to collapse
Hey are u trying to do it with rom manager?
Sent from my GT-S5570 using xda premium
debsattam said:
Hey are u trying to do it with rom manager?
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
was trying with CWM. Anyway I was able to upgrade to Gingerbread and then flashed new EmanoN rom based on gingerbread and everything went ok.
Thanks for the help anyway!
what are the modem issues? because i think i face modem issues but i cannot find a thread where somebody has issues like mine
This is an outdated thread. Please go HERE instead
{
"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've put together an unofficial ClockworkMod Recovery 6.0.1.1 until Koush adds to ROM Manager, tested working for all features except SD card mount. Working on the latter at the moment.
UPDATE: This recovery does work for both GT-N8000 (3g version) and GT-N8013 (wifi version), just confirmed. (8/16/2012)
Notes:
v1 - Touchscreen is a bit if when you have to scroll, please use the volume buttons for scrolling otherwise you may get accidental presses.
Changelog:
v1 - Everything working except SD card mount. You can backup/restore/ROM to internal or external SD card and other CWM features functional.
Flash this in ODIN or Heimdall:
Download HighOnAndroid v1 ClockworkMod Recovery 6.0.1.1
Also, here's stock recovery you can flash in ODIN or Heimdall to revert (and get OTA updates):
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/N8000_StockRecovery.tar
Credits:
Of course to Koush! I used his builder then hacked graphics.c + other files to make it work.
reserved
reserved
Amazing! Can't wait to get my hands on my Note
Sent from my SCH-I535
Way to go buddy!
You built it off builder.ClockworkMod.com, didn't you?
Sent from my GT-P1000
cdesai said:
You built it off builder.ClockworkMod.com, didn't you?
Sent from my GT-P1000
Click to expand...
Click to collapse
I did initially but had to hack it to make it work.
zedomax said:
I did initially but had to hack it to make it work.
Click to expand...
Click to collapse
Hey Zedo! Check your PM !
I noticed it does not actually backup system.img on my device, nor did any of my attempts from the clockworkmod builder site either. It says it, but skips over in reality. This will be important to fix if indeed it is not backing it up...
EDIT: Nevermind... I guess the system.img was hiding from me
Where can I find the backup? From my Tab 10.1 I was used to find it in clockworkmod on the sdcard...
akxak said:
Where can I find the backup? From my Tab 10.1 I was used to find it in clockworkmod on the sdcard...
Click to expand...
Click to collapse
It's in your clockworkmod/backup directory. Now, with the new CWM, it stores backups as pieces of files under clockworkmod/blobs directory. This saves a ton of time when doing multiple backups as "blobs" store bits of your filesystem so when doing similar backups, it's not going to backup everything again.
Make sure you copy the whole clockworkmod folder to hard disk for moving though due to this new blobs feature. Your backup folder sizes might be much smaller because of this blobs thingee.
zedomax said:
I used his builder then hacked graphics.c
Click to expand...
Click to collapse
???
Please tutorial graphics.c ...Thanks by Notonlyeyes
I tried flashing with odin following the procedure on the video and with heimdall also, but when I boot in the recovery there is the stock one...both odin and heimdall say the flash is successful and the binary count increases...I also of course tried downloading the recovery again...any suggestions?
gol-D said:
I tried flashing with odin following the procedure on the video and with heimdall also, but when I boot in the recovery there is the stock one...both odin and heimdall say the flash is successful and the binary count increases...I also of course tried downloading the recovery again...any suggestions?
Click to expand...
Click to collapse
Did you do:
Code:
heimdall flash --recovery recovery.img
There is still no clean return-to-stock package available for the N8013: Could someone who has installed this recovery and NOT rooted their device or made any other modifications to /system please go into recovery, change the backup format to tar (it's in the backup/restore menu), and do a backup? Then please post system.ext4.tar
That will get us a stock unmodified system (including proper permissions and such), which can then be rooted and flashed in Odin to get stock unmodified kernel/recovery images. Unlike the N8000, the N8013 does not yet have a stock image available anywhere.
Zedomax......greatstuff...root access on the N8010 no problem at all
....................................................................................................
Entropy512
Will try to do this now... But it'll be N8010.
Ive got the file for the N8010 on my desktop, but XDA isnt letting me upload the file keeps failing - any thoughts?
Dc
Sent from my GT-N8010 using Tapatalk 2
Entropy512 said:
There is still no clean return-to-stock package available for the N8013: Could someone who has installed this recovery and NOT rooted their device or made any other modifications to /system please go into recovery, change the backup format to tar (it's in the backup/restore menu), and do a backup? Then please post system.ext4.tar
That will get us a stock unmodified system (including proper permissions and such), which can then be rooted and flashed in Odin to get stock unmodified kernel/recovery images. Unlike the N8000, the N8013 does not yet have a stock image available anywhere.
Click to expand...
Click to collapse
Just use this bud:
http://stockroms.net/file/GalaxyNote10.1/rooted/N8013/StockROMs.net-GT-N8013RootInjectedSystem.zip
And remove /system/xbin/su and /system/app/Superuser.apk
Other than those two files, it's completely stock I pulled off my stock N8013.
I could reupload it but it would be the exact same thing as removing the two files.
zedomax said:
Just use this bud:
http://stockroms.net/file/GalaxyNote10.1/rooted/N8013/StockROMs.net-GT-N8013RootInjectedSystem.zip
And remove /system/xbin/su and /system/app/Superuser.apk
Other than those two files, it's completely stock I pulled off my stock N8013.
I could reupload it but it would be the exact same thing as removing the two files.
Click to expand...
Click to collapse
That does the trick. So far I only saw your N8000 dump. .tar would be preferable due to permissions issues, but that issue is fixable with a little bit of time.
I did the same thing with I777... Right now the only RTS packages I have are rooted ones since it's so easy to remove. I really should reupload 100% clean packages (I used to have them, and then the MegaUpload fiasco killed ALL the damn mirrors and I haven't gotten around to reuploading...)
Edit: Oh, it's a zipped-up .tar - misleading, I usually name those either .tar.7z (using 7-zip to compress) or just .tar.gz or .tar.bz2 (standard compressed tarballs)
Entropy512 said:
That does the trick. So far I only saw your N8000 dump. .tar would be preferable due to permissions issues, but that issue is fixable with a little bit of time.
I did the same thing with I777... Right now the only RTS packages I have are rooted ones since it's so easy to remove. I really should reupload 100% clean packages (I used to have them, and then the MegaUpload fiasco killed ALL the damn mirrors and I haven't gotten around to reuploading...)
Edit: Oh, it's a zipped-up .tar - misleading, I usually name those either .tar.7z (using 7-zip to compress) or just .tar.gz or .tar.bz2 (standard compressed tarballs)
Click to expand...
Click to collapse
Well, I am just waiting for samfirmware to upload some official images, rather enjoy some of my note 10.1 first for awhile, it's pretty fascinating device, I've never used a tablet for a long time before getting this one, makes my life more productive. Yeah, what's up with Megaupload, that move by feds should have been illegal.
I have a few questions about root and I was hoping someone could help. I am fairly new to rooting. I have a galaxy nexus that i use CWM Recovery and have root. I need to root my Note but I am not familiar with the binary counter (all is a little different than the nexus was). If I Flash this CWM recovery and root after will the binary counter increase? is the only way to prevent binary counter to inject root? (all CWM will cause it to increase?)
I know i am a noob but any insight would be greatly appreciated!
Thanks guys!
greenzkool said:
I have a few questions about root and I was hoping someone could help. I am fairly new to rooting. I have a galaxy nexus that i use CWM Recovery and have root. I need to root my Note but I am not familiar with the binary counter (all is a little different than the nexus was). If I Flash this CWM recovery and root after will the binary counter increase? is the only way to prevent binary counter to inject root? (all CWM will cause it to increase?)
I know i am a noob but any insight would be greatly appreciated!
Thanks guys!
Click to expand...
Click to collapse
Flashing a recovery or kernel image in Odin will cause the binary counter to increase.
Flashing it using dd or Mobile Odin from a rooted system will not make it increase.
So the "safest" way to root is currently to flash that root-injected system image linked a few posts above, as it's fully unrootable and won't trigger the counter.
I have visitors most of this weekend so won't be able to do much work - once I get my kernel source tree properly set up I'm going to work on getting TriangleAway working on this device.
Built the CM 10.2 or JB4.3 ROM from CM sources.
Changelog:
The changes here are the regular updates that are made in the source and unlike custom ROMs, I do not cherry pick the changes. This is sort of a Nighlty build ROM. Building the ROM with Linaro 4.8 for Speed.
Here are the things you should do to flash this ROM
.
1. Take a Nandroid backup of your current ROM.
2. Do a factory/data reset.
3. Flash the Rom.
4. Flash Gapps.
5. Reboot.
The above is required if you are coming from JB4.2 or before.
For those with the JB 4.3 build of 09/18/2013,
1. Reboot into recovery.
2. Wipe Cache.
3. Wipe Dalvik cache.
4. Install New JB 4.3 ROM.
5. Install Gapps.
6. Reboot and enjoy.
BaseBand Unknown: If you get baseband unknown and no GSM connection,do the following:
If you have root explorer,
1. Open the RootExplorer.
2. Go to sdcard folder.
3. Go to backup folder.
4. go to efs folder.
5. copy nv_/data.bin and nv_data.bin.md5
6. go to root ("/")
7. click on "Mount R/W"
8. open efs folder.
9. paste the copied nv_data. bin files,
10 reboot.
Note: if you dont have Root explorer, download it from the playstore.
ScreenShots:
{
"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"
}
Build Date 02/06/2014
ROM
https://www.mediafire.com/?9z491koio3zh546
Build Date 01/02/2014
ROM
https://www.mediafire.com/?f468p2bifba626x
Build Date 12/30/2013
ROM
https://www.mediafire.com/?3o1bcr9yx14glzc
Build Date 12/20/.2013
ROM
https://www.mediafire.com/?pbssrae3bkg6bvk
Build Date 12/12/1013
ROM
https://www.mediafire.com/?oaoje5urrzhkad6
Build Date 12/04/2013
ROM
https://www.mediafire.com/?3iekdr9ol5f22b6
Build Date
ROM
https://www.mediafire.com/?phuc04ne1038p8m
Build Date 11/27/2013
ROM
https://www.mediafire.com/?9vca42qccgwgdui
Build Date 11/24/2013
ROM
http://www.mediafire.com/download/d60ju4orokua6fm/cm-10.2-20131124-SADANAND-vibrantmtd.zip
BuildDate 11/22/2013
ROM
http://www.mediafire.com/download/v9nto0cqmi2s5yg/cm-10.2-20131122-SADANAND-vibrantmtd.zip
Gapps
http://www.mediafire.com/?gw54qqpqw20lced
Super Su
This app seems to work better with android 4.3. Flash this from the recovery.
http://forum.xda-developers.com/attachment.php?attachmentid=2390755&stc=1&d=1384388269
GPS:
If GPS does not work for you. Use FasterFix app to configure your location. You could you a customized gps.conf too.
Files for ODIN back to STOCK ROM.
TAR
http://www.mediafire.com/?h8hel72wrm6x487
PIT
http://www.mediafire.com/download/iqcguoi3bg39z64/s1_odin_20100512.pit
Disclaimer: Due to GPS files, that there could be intermittent E911 issues. Please be aware.
Enjoy.
The download link isn't working :/
Bugs?
Sent from my SGH-T959 using XDA Premium 4 mobile app
elfabio00 said:
The download link isn't working :/
Bugs?
Sent from my SGH-T959 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry about that.
I will upload the ROM once again and fix the link.
FIXED the ROM LINK.
Awesome do you have the modded repo?
Sent from my Nexus 4 using Tapatalk 4
jrongi1 said:
Awesome do you have the modded repo?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I don't have a repo. I can zip up the files needed to fix the gps.
jrongi1 said:
Awesome do you have the modded repo?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
sada23 said:
I don't have a repo. I can zip up the files needed to fix the gps.
Click to expand...
Click to collapse
That would be great.
Sent from my Nexus 4
jrongi1 said:
That would be great.
Sent from my Nexus 4
Click to expand...
Click to collapse
Attached a flashable zip file. This file could be flashed on any JB 4.3 ROM for VIBRANT only.
I hope the great, tireless and genius developers in this forum and others would make use of these files and develop much better JB 4.3 ROMs for us all.
Thanks man, a long awaiting 4.3 release. :thumbup:
Sent from my SGH-T959 using xda app-developers app
Installed following directions with resulting Installation Abort
Toggled verification- installed ROM following directions resulted in bootloop
Installed just the ROM resulting in bootloop.
Suggestions?
installed,
baseband unknown...
gsm is not working,tried to flash modem, still can't register on the network.
livbean said:
Installed following directions with resulting Installation Abort
Toggled verification- installed ROM following directions resulted in bootloop
Installed just the ROM resulting in bootloop.
Suggestions?
Click to expand...
Click to collapse
Try reinstating your previous ROM( non J?B 4.3). Boot up and then disable GPS. Reboot into recovery and install this ROM.
good luck.
maoten said:
installed,
baseband unknown...
gsm is not working,tried to flash modem, still can't register on the network.
Click to expand...
Click to collapse
If you have root explorer,
1. Open the RootExplorer.
2. Go to sdcard folder.
3. Go to backup folder.
4. go to efs folder.
5. copy nv_data.bin and nv_data.bin.md5
6. go to root ("/")
7. click on "Mount R/W"
8. open efs folder.
9. paste the copied nv_data. bin files,
10 reboot.
Note: if you dont have Root explorer, download it from the playstore.
sada23 said:
Try reinstating your previous ROM( non J?B 4.3). Boot up and then disable GPS. Reboot into recovery and install this ROM.
good luck.
Click to expand...
Click to collapse
Installed as suggested. Booted up fine, Everything appears to be working. I'll run it for a while and let you know.
sada23 said:
Attached a flashable zip file. This file could be flashed on any JB 4.3 ROM for VIBRANT only.
I hope the great, tireless and genius developers in this forum and others would make use of these files and develop much better JB 4.3 ROMs for us all.
Click to expand...
Click to collapse
Are you sure you uploaded the right file?
There are a few differences between the flashable fix and the rom.
Sent from my Nexus 4
jrongi1 said:
Are you sure you uploaded the right file?
There are a few differences between the flashable fix and the rom.
Sent from my Nexus 4
Click to expand...
Click to collapse
There could be some changes as I tried make a flashable zip. I think that files in zip should work. I have been testing several files and combinations. Hence the files in the ROM be different.
Let me know if the zip file does not work.
Thanks.
Feedback
he it is how I installed the rom.
1. Odin to default eclair from slimbean 4.2.2 Build 8. After boot, rooted it.
2. Flashed cm 7. 2.0 stable. And let it to settle for 5 minutes.
3. Flashed This 4.3 rom. it gave the error of wrong partition layout. flashed it again to solve it.
4. It rebooted into recovery automatically with new kernel, so I flashed 4.3 again. (if yours doesn't come to new recovery automatically then use 2 buttons combo to enter into recovery, make sure you have gingerbread bootloader).
5. Flashed GPS fix files and rebooted.
6. After 5 minutes of cyanogen logo boot animation, it successfully reached home screen.
7. Changed GPS.conf file in etc directory to my region and rebooted it. But Alas baseband disappeared. Changed kernel to Gearkernel for 4.3 and all things came to right path.
8. Used GPS status to check GPS functionality and wow it really worked. just make sure you have working internet connection.
9. Wi-Fi, Bluetooth, mobile data, everything works. except gesture typing of default keyboard. to solve this change keyboard to touchpal. you can use Swype or swift key. Battery timing seems good till now. haven't checked USB storage connection to PC yet. if anyone else have checked it please let me know.
10. overall stable and smoothly fast rom.
smokey155193 said:
he it is how I installed the rom.
1. Odin to default eclair from slimbean 4.2.2 Build 8. After boot, rooted it.
2. Flashed cm 7. 2.0 stable. And let it to settle for 5 minutes.
3. Flashed This 4.3 rom. it gave the error of wrong partition layout. flashed it again to solve it.
4. It rebooted into recovery automatically with new kernel, so I flashed 4.3 again. (if yours doesn't come to new recovery automatically then use 2 buttons combo to enter into recovery, make sure you have gingerbread bootloader).
5. Flashed GPS fix files and rebooted.
6. After 5 minutes of cyanogen logo boot animation, it successfully reached home screen.
7. Changed GPS.conf file in etc directory to my region and rebooted it. But Alas baseband disappeared. Changed kernel to Gearkernel for 4.3 and all things came to right path.
8. Used GPS status to check GPS functionality and wow it really worked. just make sure you have working internet connection.
9. Wi-Fi, Bluetooth, mobile data, everything works. except gesture typing of default keyboard. to solve this change keyboard to touchpal. you can use Swype or swift key. Battery timing seems good till now. haven't checked USB storage connection to PC yet. if anyone else have checked it please let me know.
10. overall stable and smoothly fast rom.
Click to expand...
Click to collapse
Thanks for the feedback. The change in partition does provide a warning and as you did you need to flash the rom once again. You don't need to flash the GPS zip files unless you are on s ROM that has GPS issues. This ROM doesn't have GPS issues. As you did, people have to change the GPS.conf to match their region or use faster fix app.
One again, thanks for the feedback.
Guys,
I got an email from Dropbox that my Public folder lnk has been suspended due to high volume of access and hence added a new link to download from mediafire. Hope this holds.
you are welcome.
following small problems annoy me very much.
1. enabling Ksm and zram in performance settings cause baseband unknown error. to solve it i have to uncheck them and change governor to ondemand in performance settings. then rebooting solves the problem.
2. as you know i changed kernel to gear kernel 1.0.8s, upon each boot i get annoying message of Android is upgrading, staring apps. i know it is for gear settings app builtin in this kernel being checked every time. is there any way to remove this message.
3. data of half of my user apps gets deleted upon reboot, i have to restore it from titanium backup. why this happens on every boot and only to half apps.
4. sometimes baseband changes to unknown upon boot even thoughihaven't changed any setting like zram etc.
5. you mentioned s roms have gps issue. what are s roms and how to solve their gps issue.
please take out some time to help.
{
"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"
}
Code:
#include "twrp30.cpp"
/*
* 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 Recovery
* 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.
*/
Warning! Flashing custom recovery will trip your Knox!
Works:
Install ZIP
Backup
Restore
File Manager
Terminal
Mounting Partitions
OTG
MTP and Sideload(works not always)
Known Bugs:
MTP and Sideload will not works if u have SM-A300H;
When press Reboot system it just turns phone off, u need to turn it on manually
Warning! I'm not the developer, but if you have questions, you cann ask here
Developer: Mygalaxya
Download:
Google Drive
Mirror: Mega
Thanks!!! Testing in A300M. It works on A300M , but does not start the system recovery loop
Enviado desde mi SM-A300M mediante Tapatalk
thanks a lot @Intel777chanel and @mygalaxya
Edict works perfectamente en el A300M reinstalling the original firmware.
Enviado desde mi SM-A300M mediante Tapatalk
hi,
thank's a lot dudes, works on A300FU
and now we have finally the working MTP mode we need for cm12.1 roms
excellent work :highfive:
update : with this version i can't flash any .zip ( customroms ) ( stop install with error 7 ) and the second bug is it's not boot from recovery into recovery again over the restart menue . all other important funtions are testet and works on my device perfect ...please fix it, it's a very very nice recovery
best regards :good:
So just to be sure, are you sure it won't brick my phone if I flash this recovery on A300FU?
It's not stated if its for all versions or I'm mising something.
Marecki_ said:
So just to be sure, are you sure it won't brick my phone if I flash this recovery on A300FU?
Click to expand...
Click to collapse
i am using it right now. and it is incredibly flexible, especially if you mess things up ...
feels smoother too
Can I flash on top of 2.8.7.0?
Yes you can.
OP, i am having a bit of a problem, i can't get out of Recovery. I rebooted to recovery to show it to a friend, and whatever i do, it will boot in recovery only.
Rebooting "system" boots back to recovery, and powering off in TWRP powers off normally, but it'll boot again in TWRP. Even if i restart from Download mode, same issue.
The thing is, i didnt touch nor flash anything, i know for sure the system is well.
@Intel777chanel @mygalaxya any clue?
EDIT: twrp 2.8.7.0 fixes it (temporarely )
i just read 3.0.0-1 and 3.0.0-2 is out already for a few devices...?
PlutoDelic said:
Yes you can.
OP, i am having a bit of a problem, i can't get out of Recovery. I rebooted to recovery to show it to a friend, and whatever i do, it will boot in recovery only.
Rebooting "system" boots back to recovery, and powering off in TWRP powers off normally, but it'll boot again in TWRP. Even if i restart from Download mode, same issue.
The thing is, i didnt touch nor flash anything, i know for sure the system is well.
@Intel777chanel @mygalaxya any clue?
Click to expand...
Click to collapse
Hi, have you tried to flash it using Flashify ? After flashing TWRP, don't try to reboot the phone, just turn it off and then turn it on. It should boot to system normally.
mygalaxya said:
Hi, have you tried to flash it using Flashify ? After flashing TWRP, don't try to reboot the phone, just turn it off and then turn it on. It should boot to system normally.
Click to expand...
Click to collapse
You mean Flashfire right? I previously used Mobile ODIN/Flashfire, but i saw no need to use it after i strictly used Custom Recoveries.
PS, even with the Power Off feature, when i start the phone, it went to Recovery again.
Google shows One Plus One users having a very similar issue...it definitely isn't a soft brick as flashing TWRP 2 and restarting works fine.
please let me know if i can help in any way
PlutoDelic said:
You mean Flashfire right? I previously used Mobile ODIN/Flashfire, but i saw no need to use it after i strictly used Custom Recoveries.
PS, even with the Power Off feature, when i start the phone, it went to Recovery again.
Google shows One Plus One users having a very similar issue...it definitely isn't a soft brick as flashing TWRP 2 and restarting works fine.
please let me know if i can help in any way
Click to expand...
Click to collapse
No, I don't mean Flashfire, I mean Flashify (search on Play Store), you have to download it and flash the TWRP using it. Once it is flashed, power off your phone, go to download mode and then restart completely the phone. If you did this, all should work fine.
Works if using odin on top of twrp2?
First of all thank you @Intel777chanel and @mygalaxya
Duke2010 said:
with this version i can't flash any .zip ( customroms ) ( stop install with error 7 ) and the second bug is it's not boot from recovery into recovery again over the restart menue
Click to expand...
Click to collapse
Confirm both and Reboot to System turns also device off, (Reboot -> Download & Reboot -> Power Off is working) also MTP is not woking at my A300FU
Installed over Flashify at CM12.1 and at Stock Rom via Odin3 (PC) with same result. Backup and Restore works fine
Installing zip file ´/external_sd/A3 System/cm-12.1-20160119-UNOFFICIAL-a3ultexx.zip´
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
This package is for device: a3ulte,a3ultexx,SM-A300FU; this device is .
Updater process ended with ERROR: 7
Error installing zip file ´/external_sd/A3 System/cm-12.1-20160119-UNOFFICIAL-a3ultexx.zip´
Updating partiton details...
...done
[/COLOR]
Jonny_Hood said:
First of all thank you @Intel777chanel and @mygalaxya
Confirm both and Reboot to System turns also device off, (Reboot -> Download & Reboot -> Power Off is working) also MTP is not woking at my A300FU
Installed over Flashify at CM12.1 and at Stock Rom via Odin3 (PC) with same result. Backup and Restore works fine
Installing zip file ´/external_sd/A3 System/cm-12.1-20160119-UNOFFICIAL-a3ultexx.zip´
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
This package is for device: a3ulte,a3ultexx,SM-A300FU; this device is .
Updater process ended with ERROR: 7
Error installing zip file ´/external_sd/A3 System/cm-12.1-20160119-UNOFFICIAL-a3ultexx.zip´
Updating partiton details...
...done
Click to expand...
Click to collapse
the dev have forgotten the name of device
Jonny_Hood said:
First of all thank you @Intel777chanel and @mygalaxya
Confirm both and Reboot to System turns also device off, (Reboot -> Download & Reboot -> Power Off is working) also MTP is not woking at my A300FU
Installed over Flashify at CM12.1 and at Stock Rom via Odin3 (PC) with same result. Backup and Restore works fine
Installing zip file ´/external_sd/A3 System/cm-12.1-20160119-UNOFFICIAL-a3ultexx.zip´
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
This package is for device: a3ulte,a3ultexx,SM-A300FU; this device is .
Updater process ended with ERROR: 7
Error installing zip file ´/external_sd/A3 System/cm-12.1-20160119-UNOFFICIAL-a3ultexx.zip´
Updating partiton details...
...done
Click to expand...
Click to collapse
Hi, this new TWRP 3.0 uses different mount points than 2.8.7.0, on the build you are trying to flash it uses old mount points. The developer you made the ROM must now use the mount ext4 "dev/block/bootdevice/by-name/system" on META-INF, otherwise you will not be able to flash the ROM. I will update all my builds to support this new mount points.
Thanks again here you are @mygalaxya ! Regards.
Testing this for A300Y model now after flashing successfully with the old version of TWRP recovery and will report back soon.
nowheel said:
[/COLOR]
the dev have forgotten the name of device
Click to expand...
Click to collapse
It seems so.
mygalaxya said:
Hi, this new TWRP 3.0 uses different mount points than 2.8.7.0, on the build you are trying to flash it uses old mount points. The developer you made the ROM must now use the mount ext4 "dev/block/bootdevice/by-name/system" on META-INF, otherwise you will not be able to flash the ROM. I will update all my builds to support this new mount points.
Click to expand...
Click to collapse
Whether recovery mounts partitions by name or by block device should make no difference to a rom install as the Installer script takes care of correctly mounting the partitions.
Most installer scripts unmount the partitions first anyway then remount.
If it doesn't work then the Installer script is at fault.
However according to that error twrp doesn't have the right device name in its build properties to match the rom device name.
Either the device name needs changing in the twrp 'default.prop' - ro.product.device=a3ulte or just remove the 'assert' lines in the rom installer script.
Perfect recovery and I can confirm its working on A300Y but must be flashed via Odin as apps couldn't flash it for some reason.. thanks @mygalaxya
{
"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"
}
Lineage-os 18 for Redmi Note 3 pro, ported from Mi Max by @nasim7500
What's working:
----------------
Boot
Bluetooth
Camera / Camcorder
Fingerprint Sensor
FM Radio
GPS
RIL
WiFi
WiFi Hotspot
USB (ADB/MTP)
Video Playback
Touch
Sensors
Bugs:
-------
DT2W (if you need this then install magisk & use any kernel manager app)
Some hidden bug there maybe, not sure
Installation instructions:
---------------------------
Install a compatible Recovery (orangeFox recomended)
Perform a NANDroid backup of your current ROM (Optional)
Wipe system / data / cache partitions
Flash ROM & Gapps then reboot
After boot, again reboot one more time
Optional: Install Magisk for Root.
Special thanks to these guys (For help me)
----------
@MrJarvis698, @trax85, @Jrchintu @Magicxavi
Also This guy for Testting this Rom
-----------------
@JeSsyB007, @H39AR
BUG FIXING FULL CREDIT: OUR GOD (Allah)
NOTE:
We are not responsible for bricked devices, dead sdcard, etc
If you find any other bug you can tell me, I will try to fix but no promises
All mejor bug fixed, now enjoy!!
if you face rendom reboot problem then just format data partition after install this Rom, from twrp thnx to @QantivirusP & @Ardityo
you want selected text feature in normal version? click here
This is my first post in xda so if somthing i wrong then tell me
Still alive poor battery backup then just flash this kernel
chines character kernel have obb bug
SCREENSHOTS:
A11 screen shot - Google Drive
drive.google.com
ROM Download Link:
------------------
lineage-os-18.1_ported_for_kenzo_by-nasim7500 25-8-2021.zip
FlameGApps-11.0-basic-arm64-20210822.zip
[MODED_ROM] lineage-os-18.1_ported_for_kenzo_by-nasim7500 24-8-2021.zip
Changelogs
25/08/2021
Fixed safetynet by default thnx to @Rajat_Prime & @sairam60
Fixed Fingerprint won't wakeup screen
Fixed weak wifi signal
Fixed weak vibration
Fixed poor battery backup again (cause min cpu value set to high) thnx to @trax85
Obb Fixed Big Thnx to @trax85 for compiling new kernel && @alonsoj636 & @Rajat_Prime for give me the Commit file
>>>>> MODE VERSION <<<<<
Gapps included
added selected text feature by default
add Solid explorer to system app thnx to @SkullMax01
1/06/2021
Fixed Camera
Fixed Fingerprint
Fixed FM Radio.
Fixed Heaing Issue
fixed Poor Battery backup
Fixed TWRP Installation error on kenzo device thnx to @nshussain (for findout why this problem)
Rom ported by nasim7500.
Guys if you like my work plz press like button & support to my helper or respect him, thank you..Now Enjoy!!
And Last i Want to say Thank you so much from my heart for All Kenzo dev for your hard & awseome Work...
Nice work bro..
ullas377 said:
Nice work bro..
Click to expand...
Click to collapse
Thank you bro.
nice
I am getting an error:
E1001 failed to update system image.
update process ended with error 1
I tried with the latest TWRP and OrangeFox recovery,
Formated data,
Flash stock boot.img.
Bootloader is unlocked.
Flashed stock Rom using the Mi Flash tool.
Nothing worked.
Other roms like RR and LineageOS 17.1 works fine.
Can anyone please suggest on this? Thanks.
surajbhanmehra68 said:
nice
Click to expand...
Click to collapse
Thanks
surajbhanmehra68 said:
nice
Click to expand...
Click to collapse
Thanks
surajbhanmehra68 said:
nice
Click to expand...
Click to collapse
nshussain said:
I am getting an error:
E1001 failed to update system image.
update process ended with error 1
I tried with the latest TWRP and OrangeFox recovery,
Formated data,
Flash stock boot.img.
Bootloader is unlocked.
Flashed stock Rom using the Mi Flash tool.
Nothing worked.
Other roms like RR and LineageOS 17.1 works fine.
Can anyone please suggest on this? Thanks.
Click to expand...
Click to collapse
1st flash orangefox recovery 2nd boot to orangefox recovery 3rd wipe system,data,catch,vendor 4th format data by type yes from orangefox recovery 5th reboot to recovery 6 try flashing Rom. & Report back here, thank you
nasim7500 said:
1st flash orangefox recovery 2nd boot to orangefox recovery 3rd wipe system,data,catch,vendor 4th format data by type yes from orangefox recovery 5th reboot to recovery 6 try flashing Rom. & Report back here, thank you
Click to expand...
Click to collapse
Thanks but it did not work,
What is your system partition size? mine is 2.5 GB.
I converted system.new.dat.br to img file and the size was 3 GB, maybe that is the issue?
Dnt
nshussain said:
Thanks but it did not work,
What is your system partition size? mine is 2.5 GB.
I converted system.new.dat.br to img file and the size was 3 GB, maybe that is the is
Click to expand...
Click to collapse
nshussain said:
Thanks but it did not work,
What is your system partition size? mine is 2.5 GB.
I converted system.new.dat.br to img file and the size was 3 GB, maybe that is the issue?
Click to expand...
Click to collapse
Don't know but this zip install in my device just fine without any error,,, okay I will update my post letter && fix this issue
I was able to reduce img file size using Ubuntu and flash it. Then resized system partition.
Thank you for Android 11 on Kenzo.
nshussain said:
I was able to reduce img file size using Ubuntu and flash it. Then resized system partition.
Thank you for Android 11 on Kenzo.
Click to expand...
Click to collapse
Could you please tell me that how did you reduced the img size? I'm facing at the same error says
update process ended with error 1.
xykshun said:
Could you please tell me that how did you reduced the img size? I'm facing at the same error says
update process ended with error 1.
Click to expand...
Click to collapse
Install Ubuntu os on a VM, copy img file you converted over there.
On terminal browse to location where you saved img and run commands:
e2fsck -f -y system.img
resize2fs -M system.img
Copy img from Ubuntu to computer and then phone. (I used internet, couldn't understand how to copy directly)
From recovery:
flash system.img to system partition.
Reboot to recovery.
Mount system partition,
Resize system partition.
Install gapps.
Dont forgot to flash boot.img to boot partition as well.
Regards,
removed
nshussain said:
Here is the link for the file I converted.
https://drive.google.com/file/d/1xEwm_cYJvatXSwq0P0WgWL2RhagMJMR-/view?usp=sharing
I think 16 GB Kenzo variant has only 2.5 GB system partition and that's why this issue is coming.
Click to expand...
Click to collapse
Thank you for your detailed instructions. The system.img worked perfectly to boot into the system. LOL
But I can't resize the partition, and I don't know the reason. And obviously it went wrong when I'm trying to flash gapps.
It says that
system available size: 0 KB
/product available size: 0 KB
I know the storage might not be enough, but at least it can't be 0KB.
nshussain said:
I was able to reduce img file size using Ubuntu and flash it. Then resized system partition.
Thank you for Android 11 on Kenzo.
Click to expand...
Click to collapse
your Welcome
nshussain said:
Install Ubuntu os on a VM, copy img file you converted over there.
On terminal browse to location where you saved img and run commands:
e2fsck -f -y system.img
resize2fs -M system.img
Copy img from Ubuntu to computer and then phone. (I used internet, couldn't understand how to copy directly)
From recovery:
flash system.img to system partition.
Reboot to recovery.
Mount system partition,
Resize system partition.
Install gapps.
Dont forgot to flash boot.img to boot partition as well.
Regards,
Click to expand...
Click to collapse
nice job brother
xykshun said:
Thank you for your detailed instructions. The system.img worked perfectly to boot into the system. LOL
But I can't resize the partition, and I don't know the reason. And obviously it went wrong when I'm trying to flash gapps.
It says that
system available size: 0 KB
/product available size: 0 KB
I know the storage might not be enough, but at least it can't be 0KB.
Click to expand...
Click to collapse
Post are updated && issue fixed
Thank you,
for some reason Clash of Clans hangs a lot of times on this Rom, what could be the reason?
Pubg works fine. strange.
Once I flashed this ROM, I launch it into the system, it immediately throws it into Fastboot mode!
At first I tried to flash the latest version with twrp. (I did it all by instrumentation. The effect is the same!)
And then I switched from twrp to ofrp, using the earlier version ofrp. (I did it all by instrumentation. The result is zero!)
My kenzo phone with 2gb RAM.