Database Develop

[Q] how to root and installing CM 10.1.2 on i9000

I searched for more than 3 hours to root and install CM 10.1.2 on my Samsung Galaxy S i9000
but i dont find anything good i lost my mobile :crying: then it works again :silly:
my mobile information:
GT-I9000
Firmware Ver: 2.3.3
Baseband Ver: I9000JHJV9
Build number: GINGERBREAD.JHJVG
Thank you.

i found it to use these files and kernels
https://app.box.com/shared/z2jmmzres0
a video but in Arabic
http://www.youtube.com/watch?feature=player_embedded&v=6WiuaSlKYC8#t=244
is it right????

sycolon said:
GT-I9000
Firmware Ver: 2.3.3
Baseband Ver: I9000JHJV9
Click to expand...
Click to collapse
Follow this and root only after your firmware is 2.3.6
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

Use Samsung Kies and update your phone to a newer build.
Download a root package from here (search for your build after the update) : http://forum.xda-developers.com/showthread.php?t=788108
Download odin3 1.85 and flash the rom (in odin only put the tar file in the pda box - the phone has to be in download mode {volume down+power+home pressed}) .
Go online (google play) on the phone and download the clockwork mod and install it.
Download the latest stable CM10.1.2 from here: http://download.cyanogenmod.org/?type=stable&device=galaxysmtd
Put the cm10 archive on the sd card and power off the phone.
Enter in the recovery mode (volume up + power + home) and using the volume select Wipe Data/Factory Reset and in advanced Wipe Dalvik Cache. Go back and select install zip from sd card. If it's done quick do the install from zip again.
The full tutorial here: http://forum.xda-developers.com/showthread.php?t=1494493
Do the root like i said because it's easy and then follow the guide from point 4 "• Using the volume buttons to navigate up and down select..."
After search for a google play app pack (gapps) and put it in the sd card and install it using recovery mode.
I did this yesterday and it works great.

i made the same as i told you in the last post
"i found it to use these files and kernels
https://app.box.com/shared/z2jmmzres0
a video but in Arabic
http://www.youtube.com/watch?feature...uaSlKYC8#t=244
is it right????"
and i installed CM 10.1.2
and all i s ok for now, i have 2 problems no service and the mobile reboot from its own when i dont use it....crazy

is it possible that i have the problem cuz i didänt make Lag Fix for it????

do you have the clockwork mode installed?
go back in recovery mode and wipe data/dalvik again and install cm10 again.
sycolon said:
is it possible that i have the problem cuz i didänt make Lag Fix for it????
Click to expand...
Click to collapse

yes i have it... i will try .... do i install CM 10.1.2 ?

Yes.

i tried to make it but still the same problems

i made the CM 10.1.3 and still the same problem, automatic rebooting wjen i dont use the mobile and no service .....

yes finally i fix it, thanks guys for all, but i did it in my way yeaaaaaaaaaaaah

Does it work? Are you happy with CM?:good:
sycolon said:
yes finally i fix it, thanks guys for all, but i did it in my way yeaaaaaaaaaaaah
Click to expand...
Click to collapse

yes i'm using the CM 10.1.3 Rc2 and its fantastic........... i love it

the only thing i found weird in the CM that he mentioned that the memory is 368MB just of 512MB !!!!

sycolon said:
the only thing i found weird in the CM that he mentioned that the memory is 368MB just of 512MB !!!!
Click to expand...
Click to collapse
Don't worry about that. Part of memory has been reserved by the CM. You may like the CM10.2, it is in nightly stage but even faster than 10.1.3 and you will have about double battery life. But read very carefully whole first post before installing it. It is bit odd way comming from cm10.1.3
Or quote my text (reply this e-mail) and I will send you the workflow, it isn't absolutely clear written in the opening post ofnthe thread.

tetakpatak said:
Don't worry about that. Part of memory has been reserved by the CM. You may like the CM10.2, it is in nightly stage but even faster than 10.1.3 and you will have about double battery life. But read very carefully whole first post before installing it. It is bit odd way comming from cm10.1.3
Or quote my text (reply this e-mail) and I will send you the workflow, it isn't absolutely clear written in the opening post ofnthe thread.
Click to expand...
Click to collapse
thanks you so much then i wish to have the instructions about upgrading to 10.2

Update-Desc http://forum.xda-developers.com/showthread.php?t=2385178
The rest of RAM is reserved for audio/video coding ,example camera for HD-mode and kernel for the linux system
Some Kernel support RAM up to 408MB but with no HD-support then...
sycolon said:
the only thing i found weird in the CM that he mentioned that the memory is 368MB just of 512MB !!!!
Click to expand...
Click to collapse

More information about RAM (in example the semaphore kernel ...http://www.semaphore.gr/how-to/use-semaphore-jb
"Bigmem
When the kernel boots, it reserves some RAM to be used by some drivers (video, capture, JPG) for DMA (Direct Memory Access). In Linux kernel this reservation have to be done only during boot. It was found that using less reserved memory for video capture, the kernel can operate normally without issue with the only regretion that 720p video recording is not possible. Enabling this option will leave ~13MB more available RAM.
Phone must be rebooted to enable this feature. After the device powers down the information about this option is lost and you have to reboot the phone again.
Default: Disabled"
freakymod2120 said:
Update-Desc http://forum.xda-developers.com/showthread.php?t=2385178
The rest of RAM is reserved for audio/video coding ,example camera for HD-mode and kernel for the linux system
Some Kernel support RAM up to 408MB but with no HD-support then...
Click to expand...
Click to collapse

Upgrade workflow to the CM 10.2
sycolon said:
thanks you so much then i wish to have the instructions about upgrading to 10.2
Click to expand...
Click to collapse
Ok, from CM10.1x it should work like this:
This is the thread of CM10.2 development for the i9000:
http://forum.xda-developers.com/showthread.php?t=2385178
Read whole the first post there.
Preparation:
Before upgrading, first prepare all this for the case anything goes off the plan (it shouldn't, but who knows...):
make nandroid backup
download zip files of your presently used ROM (cm10.1.3) and gapps for Android 4.2.2 and save them in your phone
download zip files of the new ROM you want to install (cm10.2) and gapps for Android 4.3 and save them in your phone
boot your phone into the recovery mode (CWM) and check if all zip files are visible
Now if all the files are visible you can upgrade (some CWM recovery versions can read zip files only from the external SD, some other versions only from the internal SD card, some both). If they are not visible, don't even try upgrade (and don't wipe any data) but reboot phone and move the zip files to another place (for example if they were not visible on internal SD, move them to the external SD card) and after you moved the files, do again the check like I wrote you above.
Upgrade:
make factory reset/wipe data
wipe cache
wipe dalvik cache under "advanced"
install zip of the CM10.2 nightly build (possibly you need to install twice, as it uses different re-partition and only warns the first time)
install the Gapps for 4.3 right after, while still in recovery
while still in recovery go to "advanced restore" and restore only /data from your last nandroid backup of the cm10.1.3
go back to first menu, reboot
enjoy, all your data from presently used cm10.1x build should be there, including Google account
If anything should go wrong, make the same procedure like you did for the installing CM10.2, wipe all and make factory reset, after that just instead of the CM10.2 zip flash your CM.10.1.3 zip and gapps for Android 4.2.2, reboot, boot again to recovery, restore your whole nandroid backup of the CM10.1.3 build.
Let me know if it worked well

[Recovery][Unofficial]TWRP 3.0.0-0 for Samsung Galaxy A3

{
"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

[ROM] [8.0.0] [yuga] LineageOS 15.0 for Xperia Z (Unofficial)

{
"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"
}
Disclaimer:
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. Hard. A lot.
*/
About ROM:
This is Experiemental Build of Android 8.0 Oreo for Sony Xperia Z (C6602, C6603), Based on LineageOS.
Thanks To:
Mardon
What's working:
* ROM is experiemental and is not recommended for daily usage *
* Now we have working Audio *
I have not tested whole rom but everything works fine except:
- Flashlight and Camera
- Adaptive Brightness
Please report any bugs in the comments below!
(Special) Install Instructions for Newbies:
Warning: If you flash ROM first time do it at your own risk, You may brick device.
Before resuming remember these things:
- You can't restore TA codes on a custom ROM, TA codes only work on Stock ROMs, So if you ever reflash Stock ROM you can restore them.
- If you're Windows 8/8.1 or 10 User this Tutorial may not work for you as long as you've done This Tutorial
- Read everything Carefully, I wish you Good Luck
1.0 - Backing up TA Codes
- First you need an unlocked bootloader, But before unlocking it you have to backup DRM keys (Optional)
- Download KingoRoot, Root your device with One-Click-Root and then Download Backup-TA Program from Here
1.1 - Unlock Bootloader
- After you've done that, Unlock your bootloader from Here
1.2 - Preparing Drivers
- After you unlock your bootloader Install Sony Flashtool from Here
- Go to Flashtool Folder then go Drivers folder and select Flashtool-drivers.exe
Check the Fastboot and Flashmode drivers then Scrool down and find Xperia Z SO-02E drivers, Check it and Install them.
1.3 - Installing ADB
- Now it's time to download ADB 15 Seconds Installer from Here
Follow the instructions in the program and Install ADB/Fastboot drivers, then locate "C:/adb" folder and open it.
- Download Latest TWRP 3.1.1 from Here and move into adb folder located in "C:/adb"
- Rename TWRP 3.1.1 file to twrp (If your file extensions are shown twrp.img)
- As long as you can't flash TWRP directly as Recovery you must flash it as boot, Your ROM won't start again so back up everything before restarting to ADB!
- After you back up everything just enable USB debugging in your phone (go Settings/About and press Build Number couple times)
- Press Back button and go to Developer Settings and find USB Debugging, Enable it.
- Now go to "C:/adb" and press and hold SHIFT, Then press RMB (Right Mouse Button) and press open command window here.
- Congratulations! Now you're in adb.
1.4 - Flashing TWRP
- Write next ADB Commands:
adb devices (so you will check your device is detected by ADB or not, If adb shows any number row and then DEVICE its okay, If it doesn't then just write):
adb reboot bootloader (Look at your phone and give permissions of USB Debugging to PC, If phone reboots it means you've done everything correctly, If it doesn't then you did something wrong!)
- Well if the phone rebooted you will see blue led in the top of your phone, That means you're in a bootloader!
Write next commands:
fastboot devices (And check your device is detected by fastboot or not, same thing it will show number row and then FASTBOOT, So you did everything correctly, If it doesn't check your installed drivers, You may have little update from Device Manager so comment down below, If drivers are installed wrong and you don't see device number and FASTBOOT just restart phone and wait for the answer in the comments)
- If you see your device number and FASTBOOT enter next commands:
fastboot flash boot twrp.img
- After you've done that and you see that it has flashed without any Errors write next command:
fastboot reboot
- Now you're in TWRP recovery, Congratulations !!
1.5 - CleanFlashing ROM
- If you backed up everything just see if your computer detects your phone's MTP (media file transfer)
Go to My Computer/Xperia Z and see is there Internal Storage or not
- If There is any Storage that's good so make a Fully Clean Install
- Go back in the main menu of TWRP press Wipe, Advanced Wipe and check: Data, Cache, Dalvik Cache, System and Internal Storage, Then swipe to wipe.
- After you wiped your phone go back to the main menu of TWRP, Enter your internal storage folder from your PC and move ROM, Gapps and Rootkit in there.
- After that Press Install, You'll see lineageos, gapps and rootkit in the TWRP so press lineageos file and swipe to flash.
- Then go back (Don't Reboot) and press gapps file, flash it as you flashed lineageos.
- Go back again and flash Rootkit but when it's finished just press wipe dalvik cache and swipe to wipe it!
- After you've done that press Reboot phone.
- Congratulations!! Wait for 10 minute to boot and enjoy your new Android 8.0.0 Oreo!
1.0-2 - Troubleshooting
- If you want to install any other Custom ROMs just resume this tutorial from ADB (adb reboot bootloader) And do the same.
- If ROM doesn't boot up that means you did something incorrectly, So you have to do next steps:
Long Press Power Button and Volume UP, After it vibrates it will vibrate three more times and then release so your phone will shut down.
Get your USB Cable which's connected to PC and hold Volume UP, then connect USB Cable into phone
- You're in a fastboot, resume tutorial from (fastboot flash boot twrp.img)
- If you flashed ROM again and still doesn't work change your gapps version and download gApps-Pico
- Then it will work 100%, Or you can flash LineageOS14.1 and wait for Stable Oreo build.
- Thank you for attention, do it at your own risk and good luck
Downloads:
MOD EDIT: Download link removed.
Download the gApps (ARM, 8.0, Pico)
Download Rootkit if you want (I've tested Magisk and works fine)
- Links updated & No more error7 in TWRP
Short Install Instructions:
Move the ROM/GAPPS/ROOTKIT on your SDCARD
Flash latest TWRP (If you have old version already reflash it using flash image)
Wipe Cache, Data, Dalvik cache and System
Flash ROM
Flash gApps
Flash Rootkit
Wipe dalvik cache
Reboot!
- First boot may take some time for optimizing apps, bootanimation may have a little lag, be patient and wait.
ROM Information:
ROM Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information:
Status: Experiemental
If you like the ROM please hit that Thanks button and give some support

Again hard work on design of topic, i hope you enjoy highlights and green (LOS color) design
So hit that THANKS button <3

#iLiKo said:
Again hard work on design of topic, i hope you enjoy highlights and green (LOS color) design
So hit that THANKS button <3
Click to expand...
Click to collapse
omg I can't believe this @@
thank you so much for your awesome work ^^

with 3.0.2- version of TWRP gave me error 7 and not install me the ROM so it is possible with 3.1.1 version ?

404 not found
Can't find it!
If you are seeing this error page then the file in question has been deleted from the site and servers. Please contact the developer/uploader for a new link to the file.

cyparisss1 said:
with 3.0.2- version of TWRP gave me error 7 and not install me the ROM so it is possible with 3.1.1 version ?
Click to expand...
Click to collapse
Not TWRP problem at all, don't delete rom because mby link got broken, ill help you to fix tommorow, update-script must be changed

Mardon deleted both international testbuilds of lineage15yuga from his account, idk why.
Link of old version:
MOD EDIT: Removed download link

not happen
with version 3.1.1
installing zip file /sdcard/Android 8/lineage-15.*****
checking for digest file....
skipping digest check : no Digest file found
Warning: no file_contexts
E3004: This package is for device: C6602, C6603, C6606, yuga;this device is .
Updater process ended with ERROR: 7
Error installing zip file lineage-15*******
Updating partition details...
....done
my device is 6603 I am sure in that - how to check and set it, may be from the custom roms this information is lost in the phone ?

cyparisss1 said:
with version 3.1.1
installing zip file /sdcard/Android 8/lineage-15.*****
checking for digest file....
skipping digest check : no Digest file found
Warning: no file_contexts
E3004: This package is for device: C6602, C6603, C6606, yuga;this device is .
Updater process ended with ERROR: 7
Error installing zip file lineage-15*******
Updating partition details...
....done
my device is 6603 I am sure in that - how to check and set it, may be from the custom roms this information is lost in the phone ?
Click to expand...
Click to collapse
dude its bugged at update-script so tommorow when i get PC please upload that new ROM somewhere, ill fix it and you and other people can download back, i fixed the link, but its old version without audio..

#iLiKo said:
Mardon deleted both international testbuilds of lineage15yuga from his account, idk why.
Click to expand...
Click to collapse
I can tell you why. Because you posted it without even asking. This happened a month ago too. Please stop that. It is annoying and delays LOS15 for fusion3 because people have to deal with this sh**.

I am using custom rom and my device model is Xperia Z , it is possible to not verify my phone like c6603 and then the installation fails. See on the screen shots

#iLiKo said:
dude its bugged at update-script so tommorow when i get PC please upload that new ROM somewhere, ill fix it and you and other people can download back, i fixed the link, but its old version without audio..
Click to expand...
Click to collapse
welcome my friend, MOD EDIT: Removed download link

NamenIos said:
I can tell you why. Because you posted it without even asking. This happened a month ago too. Please stop that. It is annoying and delays LOS15 for fusion3 because people have to deal with this sh**.
Click to expand...
Click to collapse
ill explain u smth this rom is shared and doesnt require any rights to post on websites, also people must have single oreo rom for this phone to try how its like, plus i made whole tutorial of newbies now i think they wont get in problems, also everyone knowns that this is experimental testbuild, but LOSTEAM still want to share only stable.. i think differently, i think people can see how oreo really is, whats the differences and etc.. by themselves. stop it, im not gonna delete rom again.

cyparisss1 said:
welcome my friend, MOD EDIT: Removed download link
Click to expand...
Click to collapse
new link: MOD EDIT: Removed download link

Bug
Camera not working
Lag ui (recent app)
Error 7 script delete assert line

mohammadnadimi48 said:
Camera not working
Lag ui (recent app)
Error 7 script delete assert line
Click to expand...
Click to collapse
Error 7 has been fixed i think so.
Use new link

Thread closed.
#iLiKo said:
ill explain u smth this rom is shared
Click to expand...
Click to collapse
Yes, you are right here - LineageOS can be built from source.
#iLiKo said:
doesnt require any rights to post on websites
Click to expand...
Click to collapse
Not quite correct - you still need to stick to the XDA rules (see rule 12).
You need to accept the fact that the developers of the ROM don't want to release half-baked builds or unfinished work (even if it's open source). Don't we all want a stable daily driver after all?
Thread closed.

[RECOVERY][on7xelte] TWRP 3.3.0 for Galaxy J7 Prime

Team Win Recovery Project​
{
"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 <std_disclaimer.h>
/*
* 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 doing this to your device
* 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.
*/
Disclaimer:
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox TZ Features. It can't be reset in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
- If you like my work please hit the "Thanks" button to support me. You're also free to donate me via my donation link here in XDA.
Installation:
- Download Odin3 v3.13.1, Samsung USB Drivers, latest TWRP's tar for your variant, latest no-verity-opt-encrypt zip and copy all of them to your internal storage.
- Go to Settings App, Developer Options and enable OEM Unlock (If you don't see Developer Setings, go into About phone>Software info and tap "Build number" 10 times to show Developer Options menu).
- Do a backup of all your important data and files in your phone.
- Shutdown the phone. Once it's off, Power it On in Download Mode (Press and hold Vol DOWN and Power buttons together )
- Open Odin3, go in Option section and untick "Auto-reboot". Once that click the "AP" button and select the TWRP tar you downloaded before, then press the "Start" button.
- Once Odin3 finished to flash the recovery (you should see a "PASS" message), force reboot your phone (Press and hold Power and Vol - buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
- Once TWRP is booted you first need to decrypt your /data partition. To do so touch Wipe>Format Data and follow the instructions in screen.
- Once it finished go back at the home screen and touch Reboot>Recovery. TWRP should be able to mount your data partition. Now flash the no-verity-opt-encrypt zip you downloaded before (touch Install and select each zip to flash it)
- You're now able to reboot to your OS without re-encrypting /data partition .
Download:
TWRP 3.3.0 (taking down due to a bug, will fix and upload asap)
TWRP 3.2.3
Previous Builds:
TWRP 3.2.2
TWRP 3.2.1
TWRP3.2.0
Bugs:
Cannot mount External SD Card in TWRP
Changelog:
17 April, 2019 (TWRP 3.3.0)
Updated to TWRP 3.3.0.
Read full changelog over here and here.
Credits:
- Samsung Open Source Centre for kernel source code
- TeamWin for their awesome recovery

Awesome work bro thanks for Ur efforts, can you plzz try to fix that bug :fingers-crossed:

Wth ? Ss show that the version is 3.0.0 !

I need this recovery in the formats. img, please don't have a computer[emoji120]

al.iraq said:
I need this recovery in the formats. img, please don't have a computer[emoji120]
Click to expand...
Click to collapse
Root explorer to extract the tar or zarchive
Sent from my Samsung SM-G955F using XDA Labs

Demicro said:
Root explorer to extract the tar or zarchive
Sent from my Samsung SM-G955F using XDA Labs
Click to expand...
Click to collapse
Thank you very much sir, I forgot this. Now remember it thanks again[emoji257]

I can't seem to get the interface to navigate any of the partitions or data directories.
If I move the supersu zip to the phone, I can't find it at all, if I try to mount an sd card, it mounts the wrong file contents somehow.
Something is wonky with the disks

does support SM G610Y?

Working fine.

TWRP 3.2.1
CHANGELOGS
-F2FS support
-Updated TWRP to 3.2.1

DarkLord1731 said:
Team Win Recovery Project 3.2.1
HOW TO INSTALL
Install via ODIN in AP section
OR
If you have TWRP already installed you can extract the downloaded tar and install via recovery(INSTALL -> Select Image -> Flash)
Click to expand...
Click to collapse
But to install by Odin is not it necessary that the file be MD5? How can I get a MD5 file to a first install?

Kherham said:
But to install by Odin is not it necessary that the file be MD5? How can I get a MD5 file to a first install?
Click to expand...
Click to collapse
No it isn't necessary, you can install tar files

DarkLord1731 said:
No it isn't necessary, you can install tar files
Click to expand...
Click to collapse
Am asking because I tried many times install it by Odin with a .tar file and didn't worked. Will put this one in my card for another try.
Thank you very much.

Can I flash on G610L

can you suggest me how to flash or install on this TWRP since it didnt recognize my internal and external memory :<. Tried to use USB cabble but no result too.

i need some help i install the twrp and make it work but when i am try to see any file from sd card or any i cant so i cant install this rom. SdCard Looks empty but its not

i install this recovery in samsung j7 prime odin showing succesfully install but when i try to boot into recovery it is directly boot into stock recovery. help me

no-verity-opt-encrypt.zip
Sir I was wondering on how can I install this zip "! (no-verity-opt-encrypt.zip)
I installed the recovery and it worked fine for me " thanks for that "!:laugh::good:
---------- Post added at 12:32 PM ---------- Previous post was at 12:28 PM ----------
Baqir2 said:
i install this recovery in samsung j7 prime odin showing succesfully install but when i try to boot into recovery it is directly boot into stock recovery. help me
Click to expand...
Click to collapse
Sir I installed this and working fine"!
what I did is I installed it and test to see if its working and no its not and after
I installed it again and tick the auto reboot on odin
and patch it then press and hold the combo for going into download even tho in it and after or immediately the screen goes black press the combo for going into recovery and wolla enjoy I hope this helps "!
sometimes it helps reading the instrucyions carefully "! ???

Deleted

For ppl having trouble to mount internal memory follow these steps:
You have to first Flash TWRP Recovery From Odin
Then on TWRP go to Advance>Wipe And Press Format Data And Type Yes
Then your Internal storage will be able to mount while connected to the PC
And you can now drag zips to flash on your Internal memory via PC
Running perfect on my G610Y

[RECOVERY][OFFICIAL] TWRP 3.6.0_9 [N8000 N8010 N8020]

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Odin
- Odin3 v3.10.5
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy Note 10.1
How to flash TWRP with Odin
1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down simultaneously. When the warning screen appears, release all buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP".
3. Disable auto reboot in Odin and press start.
4. You can then boot directly into TWRP by pressing the Power and Volume Up simultaneously. Release all buttons as soon as you see the boot screen ("Samsung Galaxy Note 10.1").
How to flash TWRP within a previous version of TWRP
1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power and Volume UP simultaneously. Release all buttons when the boot screen appears ("Samsung Galaxy Note 10.1").
2. In TWRP, tap "Install" then "Install Image".
3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.
4. Select the "Recovery" radio button.
5. Move the slider to the right to flash the TWRP image.
6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.
Bugs
- You tell me!
Credits
TWRP Team and all people who worked / are working on the exynos 4 devices.
Sources
- n8000 repository
- n8010 repository
- n8020 repository
- TWRP repository
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 spare time and every donation keeps me motivated.
donate
XDA: DevDB Information
TWRP 3.6.0_9-X, ROM for the Samsung Galaxy Note 10.1
Contributors
@html6405
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-1
Stable Release Date: 2021-02-14
Created 2021-02-14
Last Updated 2021-10-12

Hey after updating to this recovery I noticed when I went to wipe my /data partition it would end up wiping my internal storage even though I did not select the internal storage. Just wanted to let you know about this bug I encountered.

CurbThePain said:
Hey after updating to this recovery I noticed when I went to wipe my /data partition it would end up wiping my internal storage even though I did not select the internal storage. Just wanted to let you know about this bug I encountered.
Click to expand...
Click to collapse
What have you exactly done? If you choose wipe /data, then it should also wipe your internal memory (this is mounted in data/media).
But if you made a factory reset, then the internal memory shouldn't be deleted.

html6405 said:
What have you exactly done? If you choose wipe /data, then it should also wipe your internal memory (this is mounted in data/media/0).
But if you made a factory reset, then the internal memory shouldn't be deleted.
Click to expand...
Click to collapse
Well previously using TWRP 3.3.1 I would do the advanced wipe and only select the /data partition not the internal storage. Then it would say "wiping /data without wiping internal storage". But if I did the same thing in TWRP 3.5.0 it would say "wiping /data and internal storage". I stopped using the basic factory reset many years ago because it always wiped my internal storage. But I will give it a shot and let you know if that works for formatting just the /data partition.

CurbThePain said:
factory reset many years ago because it always wiped my internal storage.
Click to expand...
Click to collapse
This was a faulty behaviour, because the factory reset should wipe only /data withoult /data/media.

Off topic, but it seems like emojis need to be disabled in the 1st post.

TWRP 3.5.1_9-0 is now ready to download , if you should find any bugs, let me know.​

got an error
"Size of image is larger than target device"
device N8013 twrp version 3.4.0-0
running Slim 7

noobody168 said:
got an error
"Size of image is larger than target device"
device N8013 twrp version 3.4.0-0
running Slim 7
Click to expand...
Click to collapse
Thanks for testing it,
I will check on this later, maybe something went wrong in the conversion,
I will fix this and we will receive a new build.

All image sizes are fixed,
new builds are up!

html6405 said:
Все размеры изображений фиксированные,
новые постройки построены!
Click to expand...
Click to collapse
Alas, the image size is too large, not flash, n8000 (2021-03-22 09:05:36 build)

html6405 said:
Thanks for testing it,
I will check on this later, maybe something went wrong in the conversion,
I will fix this and we will receive a new build.
Click to expand...
Click to collapse
Works fine with with revised version now, thank you very much

SteelK said:
Alas, the image size is too large, not flash, n8000 (2021-03-22 09:05:36 build)
Click to expand...
Click to collapse
Are you sure? I've tested it, I will check on this later.

Yes, I'm sure I tried the latest version from TWRP site for N8000

Now I've tested the files again from both servers, and it is working in my case.
The file size is lower then our border size.

Is there any option to find out the size of the recovery partition?
Im used https://dl.twrp.me/n8000/twrp-3.5.1_9-0-n8000.img.html
How is this possible ...
The image from the tar archive was installed, but the image from the img link was not.
md5 are the same.

SteelK said:
Is there any option to find out the size of the recovery partition?
Im used https://dl.twrp.me/n8000/twrp-3.5.1_9-0-n8000.img.html
How is this possible ...
The image from the tar archive was installed, but the image from the img link was not.
md5 are the same.
Click to expand...
Click to collapse
I have no idea, actually if the md5 is the same, it must work.
SteelK said:
recovery partition?
Click to expand...
Click to collapse
Yes, but they are equal for all of us.

I seem to have lost access to my microSD in recovery..? I updated from the microSD and on reboot the card was corruptred in LOS18...I was able to fix and recover on my computer and am able to see it again in Android, but still won't mount in recovery. Any ideas?

xtoad said:
I seem to have lost access to my microSD in recovery..? I updated from the microSD and on reboot the card was corruptred in LOS18...I was able to fix and recover on my computer and am able to see it again in Android, but still won't mount in recovery. Any ideas?
Click to expand...
Click to collapse
Which file system are you using?
I had to sort out some things, TWRP needs much more space now.

html6405 said:
Which file system are you using?
I had to sort out some things, TWRP needs much more space now.
Click to expand...
Click to collapse
I believe it is ext4. Or whatever the default is. I have not changed it on my own.