Database Users

[Q] Feedback to [GUIDE] Root (Updated for ICS) #213 on page 22

Am 10 postings away from being allowed to join the original discussion.
Have ICS 4.0.4 OTA upgrade to ...-P6800XXLQ1-...
Used the procedures and data from Attached Files of posting #213 by kable in #213 in
http://forum.xda-developers.com/showthread.php?t=1454112&page=22
CWM installed well from recovery.
But CWM did not install root.zip!
Error message:
CWM Recovery v5.8.1.5
E: Can't mount /sdcard/
What could have gone wrong? What further details are needed to find a remedy? What else is needed to root successfully?

Updates:
I have found solutions after reading all posts related.
If you have just PC Odin an unrooted SGT 6800 into ICS, your SGT now cannot be rooted. What I have done thereafter is as follows:
1. PC Odin CWM 5.5.0.4 into my 6800;
2. set-up your 6800 into recovery mode ( press power & vol-up same times, release power button once your see active screen, then release vol-up button as well, you will be in CWM recovery mode;
3. goto zip from sdcard; toggle signature verification & script asserts to disable;
4. then choose zip from internal sdcard; from there you should choose root.zip ( this root.zip was saved into your external sdcard in advance.)
5. Once done, choose reboot.
Now you new ICS is rooted.

Which zip and which sdcard, that is the question.
Hi ronnieho,
thanks for your quick response and help. I am sure you will get me running. Please give me some more details which due to my lack of experience I feel to be missing.
Please let me explain this, then you will know which details still trouble me:
Last week I managed to root my ICS SGS2 following these instructions:
http://www.pocketpc.ch/samsung-gala...-stock-ics-firmware-ohne-flashen-kernels.html
It is in german, but based on the original thread
http://forum.xda-developers.com/showthread.php?t=1501719
The german instruction was very specific about which zip to put into which (internal or external) sdcard.
The english XDA instructions are not that specific about these obviously very important details.
Would you please add these details to your instructions:
1. PC Odin CWM 5.5.0.4 into my 6800;
Does this mean, place CWM.zip into the external sdcard (i.e. /sdcard/extStorages/SdCard) of the 6800?
From the threads refered to in my first post I have CWM 5.8.1.5. May this work too? Or must it be CWM 5.5.0.4? Where can I get CWM 5.5.0.4?
2. set-up your 6800 into recovery mode ( press power & vol-up same times, release power button once your see active screen, then release vol-up button as well, you will be in CWM recovery mode;
Yes, this is how I get into recovery mode.
3. goto zip from sdcard; toggle signature verification & script asserts to disable;
goto _which_ zip from _which_ sdcard.
Rooting my SGS2 I used
- install zip from sdcard
Here _sdcard_ meant the external sdcard
And _zip_ meant CWM.zip.
Is this also true for your instruction step 3?
toggle signature verification & script asserts to disable;
Where/to what item should I apply these instructions?
4. then choose zip from internal sdcard; from there you should choose root.zip ( this root.zip was saved into your external sdcard in advance.)
So far I did not save any zip to the internal sdcard?
Should I have saved root.zip into the internal sdcard in step 1?
Which root.zip? Remember, I have CWM.zip and root.zip from the Attached Files of posting #213 by kable in http://forum.xda-developers.com/showthread.php?t=1454112&page=22
Can I use these files or should I download different zip-files? From where?
Sure, I could simply try out my questions, but I am afraid to brick my Tab.
Another important detail may be that I did not use Odin to copy the zip files to the tap. In my successful rooting of the SGS2 I simply used the USB MTP connection and copied the zip-files like I copy video and audio files, and it worked. I would prefer to keep this copy practice also regarding the Tab7.7. Or must I copy with Odin? Why? Do I miss something if I copy in MTP mode? Does Odin do a different copy? Does Odin copy to different/specific sdcard locations?
I am confident that using your instruction will make the difference. Please give me the details which I feel to be missing.
Thanks!

Took the risk - Success, at last!
Since I did not get any more helpful answers, I had to reconsider the situation. Finally I decided to take the risk by using a best of
a) the xda-developers [GUIDE] Root (Updated for ICS)
http://forum.xda-developers.com/showthread.php?t=1454112
, e.g. postings #1 by Jade Eyed Wolf, #213 by kable, #227 by ronnieho, #230 by mashkuov, etc.
b) aljee77 guide for the SGS2
http://www.pocketpc.ch/samsung-gala...-stock-ics-firmware-ohne-flashen-kernels.html
Trusting that the xda-developers zip-files, CWM.zip and root.zip, will be ok for the Tab7.7
and hoping that the aljee77 procedure will also work as well for my Tab7.7 as it has worked for my SGS2,
I took the risk and finally succeeded to root my Tab7.7.
My successful procedure (Thanks to aljee77 and mashkuov):
1. Data preparation (zip-files)
1.1 Downloaded CWM.zip and root.zip to my computer from mashkuov, post #230 in http://forum.xda-developers.com/showthread.php?t=1454112&page=23
1.2 Copy these zip files from my computer to respective sdcard in my tab.
I have the Samsung Kies drivers installed on my computer. But I do not use Odin. I connect the tab and the computer with the USB data cable and simply use the USB MTP connection. I simply copy the zip-files like I would copy video and audio files by simple Windows Explorer file-drag/drop between the the source/target location icons.
1.3 I copy CWM.zip into my _external_ SDCARD
(on the computer: GT-P6800/Card
on the tab: /sdcard/extStorages/SdCard)
1.4 I copy root.zip into my _internal_ SDCARD ( /sdcard/ ) <--- aljee77 procedure <--- :good:
(on the computer: GT-P6800/Tablet
on the tab: /sdcard/)
2. Temporary installation of CWM Recovery:
- Reboot to recovery:
2.1 Download and install LATEST SAMSUNG KIES (or stand-alone USB drivers if you can find them)
2.2 Transfer CWM.zip to the EXTERNAL CARD on Galaxy Tab 7.7 (already done in step 1.3)
2.3 Turn off the Galaxy Tab 7.7
2.4 Enter Recovery
- Hold Volume UP button + Power Button
- When TAB turns ON, RELEASE POWER BUTTON (Keep Holding Volume UP Button)
* Will Enter Recovery
2.5 In the following basic menu use Volume Up/Down to navigate and Power OFF to select/accept options!
- Choose apply update from external storage.
- Choose CWM.zip and wait until CWM recovery appears.
* Now a temporary CWM is installed and activated.
* This CWM recovery is only a _temporary_ CWM and will be gone after reboot!
* see #217 by vegaman: http://forum.xda-developers.com/showpost.php?p=28300775&postcount=217
3. Install root
* Once the CWM recovery appears:
* _Touch-screen_ to navigate and to choose an option!
- install zip from sdcard (1st CWM menu)
- choose zip from internal sdcard (2nd CWM menu) <--- aljee77 procedure <--- :good:
- toggle signature verification & script asserts to disable <--- ronnieho #227 http://forum.xda-developers.com/showthread.php?t=1454112&page=22
- +++ GO BACK ++++ (from 2nd to 1st CWM menu)
- reboot system now (1st CWM menu)
* After reboot your tab will be rooted and temporary CWM will be gone.
4. Enjoy!
Now the tab is rooted! Temporary CWM is gone.
Now you can download Superuser App and Superuser Elite App (both by ChainsDD) from the market.
5. If you want a permanent CWM see #220 by Handymeister: http://forum.xda-developers.com/showpost.php?p=28319010&postcount=220
- after installing temporary CWM I flashed the root.zip with it.
- then reboot
- with root I flashed the CWM with Mobile Odin and that works fine and is now resistant again
Click to expand...
Click to collapse
6. If you need to unroot, see #5 by kazuni: http://forum.xda-developers.com/showpost.php?p=21600037&postcount=5
Re-flashing manufacturer rom through Odin is the only method as far as i know
Click to expand...
Click to collapse
Many thanks to aljee77 from pocketpc.ch and to the xda-developers posting experts in [GUIDE] Root (Updated for ICS)!
http://forum.xda-developers.com/showthread.php?t=1454112
Problem solved!

ZTE Blade L2 Kitkat Firmware

Android Kitkat based ROM for the ZTE Blade L2
SwitchBL2de
ROM Features:
PreRooted
Apex Launcher
Debloated
Micro SD switched with Phone Storage
Zipalligned
ZRAM
build.prop Tweaks for the following :
Video and Photo Quality
Internet Connection Speed/Quality
Network Performance
Download Link:
Removed - Recompiling Rom, My sincerest apologies to DeviRSilva.
I used an earlier version of his kernel for the build - http://forum.xda-developers.com/android/development/kernel-devir-blade-l216-11-2014-t2945103
MD5 : a719cb770585f24c891fe47da9e56245
Note - Updated hosts file for ad blocking (Use xposed module "hosts Enabler" to prevent adverts)
Once Rom is installed and you restart phone from recovery
It may give the following warning "Root access possibly lost. Fix? THIS CAN NOT BE UNDONE"
Select "Yes - Fix root (/system/xbin/su)"
Credits to BSDgeek_Jake for the hosts file (http://forum.xda-developers.com/showthread.php?t=1916098)
*****************************************************************************************************************************************
Custom Recovery
Please have a read through the information in this link : http://www.howtogeek.com/193055/what-is-a-custom-recovery-on-android-and-why-would-i-want-one/
Flashing a custom recovery on the L2 is a simple process.
Things Required for this process:
Rooted Phone - (Please see the post on Rooting)
Mobile Uncle Tools APK
Recovery Image
First you have to allow the phone to install apps that dont come from Google Play Store.To do so,follow the guide :
1.Settings Menu
2.Security
3.Enable(tick) Unknown sources
4.Untick Verify apps
You can always reset these back to how you found them when you are done.
Download Mobile Uncle Tools
Mega Link: http://goo.gl/IkyVDo
or
MediaFire Link : http://goo.gl/c5q6Jh
Copy APK file to your SD card,use your file manager to install it.
Run Mobile uncle tools,allow root permissions when menu pops up.
You can close the app for now.Next thing we need is the actual recovery file itself.I've attached the recovery i find works best
Carliv Touch Recovery v2.2 - MTK CWM-based v 6.0.4.4
Download Recovery.img file
Mega Link: http://goo.gl/1f8OwX
or
MediaFire Link :http://goo.gl/U1D2Zu
MD5 :9f770b95df8e1beabd7417fc112190bc
Once the file has downloaded,copy to the root of your SD Card.
Open Mobile Uncle Tools and Select "Recovery Update".
Be sure to Select the downloaded recovery image,not anything else.
Select the file and proceed with installation.Mobile uncle tools will then prompt you to reboot into recovery if the update was successful.Select Yes and the phone will reboot into the new recovery menu
Credits to :
eddy.rugal - Base Rom
Carliv - For Recovery
njava - For Mobileuncle MTK Tool

Update
Resize Apps Partition
WARNING! This can BRICK your phone if done incorrectly.
PLEASE FOLLOW ALL STEPS CORRECTLY.
Please make a backup of all your important stuff.
Make a backup in the recovery.Make 100% sure the backup completes without any errors
Reboot into recovery mode (Hold the Up button and press power button to turn device on)
1.Select Backup and Restore
2.Select Backup and Confirm(Proceed)
Once the backup is complete,the backup is located in "clockworkmod" folder on SD Card
You have to factory reset device,so be prepared to reinstall apps/games (You are going to lose data)
If you are fine with all of the above,The following mod increases the App Partition size from 1GB to 2GB.It rewrites the Internal Storage to 513MB(Used for videos/pictures,which is fine since we use our Micro SD cards for that)
If you are happy with all of the above,you can proceed with the next step :
Firstly,Download all files required and copy to SD Card
2 GB for apps_Jellybean_4.zip (232.63 KB)
Mega Link - http://goo.gl/ao3NFO
or
Media Fire Link - http://goo.gl/3j9RWm
AND
MTK_Nvram_Tool.zip (2.9MB)
Mega Link - http://goo.gl/Z2Chpx
or
Media Fire Link - http://goo.gl/sjah8X
Once on SD Card,reboot into recovery mode (Hold the Up button and press power button to turn device on)
1.Select "Install Zip"
2.Select "Choose zip Sdcard"
3.Choose "MTK_Nvram_Tool.zip"
4.Select "Yes - Install MTK_Nvram_Tool.zip"
5.Click Next
6.Select "I Agree with this Terms and Conditions" and click Next
7.Click Next again
9.Choose 'Nvram Backup"
Once its done it should say "Backup Completed"
Under that it should say "Nvram Backup Successfully Completed"
It give the location for that backup,always keep that file (Copy to the PC Later)
10.Click OK
11.Click Exit
12.Click Yes
Now you are back at the install update from zip file screen.
13.Select "Install Zip"
14.Select "Choose zip Sdcard"
15.Choose "2 GB for apps_Jellybean_4.zip"
16.Select "Yes - Install 2 GB for apps_Jellybean_4.zip"
17.Go back to main menu
18.Choose Wipe menu
19.Choose Wipe Data (Factory Reset) -THIS WILL ERASE YOUR DATA
20.Wipe Cache
21.Wipe Dalvik Cache
22.Go back to main menu and reboot phone
The phone should reboot.If you get a message saying you have to format phone storage,click yes to format.
Go to Settings,Storage and See Total space is now 1.97GB
If the phone wont boot,power down,then hold up key and turn on to get into recovery mode.
1.Select Backup and Restore
2.Select Restore and Confirm(Proceed)
Restore the backup you made earlier.
This should let the system load when you reboot again,even if it asks you to format the phone again.
Copy NVRAM Backup to PC for safe keeping.
If you want to return to original/stock
Follow the same procedure as above but use the following file instead of the 2GB File
Stock Partition_Jellybean_4.zip (232.63KB)
Mega Link - http://goo.gl/pMn0ea
or
Media Fire - http://goo.gl/KJfRF7
Credits to :
AnoopKumar - MTK Nvram Tool

Andalitez said:
Hi Guys
Just an update.I downloaded the update from the website again,used winRAR and replaced the modem file in the system.
Everything works great now
Click to expand...
Click to collapse
Hey man can u yplease hook me up with the modem file im kida stuck with unkown baseband too

Replied
BlaqueDroid said:
Hey man can u yplease hook me up with the modem file im kida stuck with unkown baseband too
Click to expand...
Click to collapse
Hey man.
Sent you a PM.Currently working on a rom,will only be able to upload it for you in afew hours

ZTE
ztedevices.com/search.html?keyword=blade l2 look on there for the firmware for your device , push via adb sideloading and you should be set

noob problem...
guys, can you please help me...I also have the same problem when I flashed the kitkat rom...my blade l2 now can't read my simcard...what should I do?...

No Sim Detected
eochi18jhae said:
guys, can you please help me...I also have the same problem when I flashed the kitkat rom...my blade l2 now can't read my simcard...what should I do?...
Click to expand...
Click to collapse
Okay,you have to download the firmware version for your country,and have custom recovery installed on the phone.
So if you in UK,download the rom for your phone from UK provider.(doesnt matter if its JB or KK)
http://www.ztedevices.com/support/index.html
Once you have the rom,Use winRAR to do the following:
1.open the rom from your country in winrar so you can see the contents.
2.Open system folder (dont extract,just navigate into the folders in winrar)
3.Open "etc" folder
4.Open Firmware folder
5.Select "modem_1_wg_n.img" and extract it(i just drag and drop on desktop)
6.Open the Kitkat firmware you've downloaded using winRAR
7.Open System folder
8.Open "etc" folder
9.Open Firmware folder
10. Copy the "modem_1_wg_n.img" into that location(drag and drop from desktop)
11.winRAR asks if you want to :Add/Replace file/s? Select Yes or OK to allow it to
12.copy entire firmware to phone and reflash it on the phone from the SD card
I dont know if you can just replace the modem file after having loaded the firmware.I didnt try or test it.it may or may not work.
I am working on Custom Firmware for this phone though.
latest achievement was i managed to get the phone to see the SD card as phone storage thanks to various xda guides.this will be built in
FIrmware should be ready in a few days after testing.if anybody is interested in trying it out,let me know

problem solved...
Thank you sir...problem solved...it's really hard to be a noob...have to understand a lot of things now....I'm willing to try your firmware on my phone...upload it when done...keep up the good work...sorry for my english...

Post has been updated

I need to talk to you.... Go read my PM

installation is always aborted.. PLEASE HELP

Replied

Thanks
The thread is so useful... Keep up the good work, I don't have patience to try the new ROM!
Is there any chance for kernel supporting overclocking and undervoltage, also with more Gvernor and I/O Sheduler options?
Also Would be gorgeous if there's tap screen to wake option, this would need custom kernel too...
I'm now using DeviRSilva's kernel, which is doing great! Man, don't be afraid to relese it and continue tweaks
Still I'm a noob and maybe half of theese wishes are impossible, but would be so cool if they're possible to develop!
PD: I saw a site promoting Lollipop ROM for our L2 is that real?
PD2: Sorry for my awful English and probably stupid requests and questions...

helpppp
I have probelm, phone do not show sim card, on official site there is no serbia rom please how to fix it?

Andalitez said:
Replied
Click to expand...
Click to collapse
It fails to flash the ROM with the updated radio file. Just stops at Can't open... file.zip '(bad)'. Installation aborted.
How to fix?

Hi how do i unroot the zte blade l2?
And how to I remove costum recovery and reinstall stock recovery and stock rom?
Thanks just asking in case of sending it back for repairing.
Just noticed that the download link has been remoded.
Can someone provide a link for this rom?
Thanks.

Does this ROM have Greek language installed ???

no links are working
I need a copy of carliv recovery and backup of stock recovery as u think although my mobile mainly working I think the recovery is corrupt and has screwed my sound thanks in advance as I am taking a giant leap and biting bullet to try this recovery hope it can flash the legit kit kat if ever released by zte or virgin UK thanks
Andalitez said:
Android Kitkat based ROM for the ZTE Blade L2
SwitchBL2de
ROM Features:
PreRooted
Apex Launcher
Debloated
Micro SD switched with Phone Storage
Zipalligned
ZRAM
build.prop Tweaks for the following :
Video and Photo Quality
Internet Connection Speed/Quality
Network Performance
Download Link:
Removed - Recompiling Rom, My sincerest apologies to DeviRSilva.
I used an earlier version of his kernel for the build - http://forum.xda-developers.com/android/development/kernel-devir-blade-l216-11-2014-t2945103
MD5 : a719cb770585f24c891fe47da9e56245
Note - Updated hosts file for ad blocking (Use xposed module "hosts Enabler" to prevent adverts)
Once Rom is installed and you restart phone from recovery
It may give the following warning "Root access possibly lost. Fix? THIS CAN NOT BE UNDONE"
Select "Yes - Fix root (/system/xbin/su)"
Credits to BSDgeek_Jake for the hosts file (http://forum.xda-developers.com/showthread.php?t=1916098)
*****************************************************************************************************************************************
Custom Recovery
Please have a read through the information in this link : http://www.howtogeek.com/193055/what-is-a-custom-recovery-on-android-and-why-would-i-want-one/
Flashing a custom recovery on the L2 is a simple process.
Things Required for this process:
Rooted Phone - (Please see the post on Rooting)
Mobile Uncle Tools APK
Recovery Image
First you have to allow the phone to install apps that dont come from Google Play Store.To do so,follow the guide :
1.Settings Menu
2.Security
3.Enable(tick) Unknown sources
4.Untick Verify apps
You can always reset these back to how you found them when you are done.
Download Mobile Uncle Tools
Mega Link: http://goo.gl/IkyVDo
or
MediaFire Link : http://goo.gl/c5q6Jh
Copy APK file to your SD card,use your file manager to install it.
Run Mobile uncle tools,allow root permissions when menu pops up.
You can close the app for now.Next thing we need is the actual recovery file itself.I've attached the recovery i find works best
Carliv Touch Recovery v2.2 - MTK CWM-based v 6.0.4.4
Download Recovery.img file
Mega Link: http://goo.gl/1f8OwX
or
MediaFire Link :http://goo.gl/U1D2Zu
MD5 :9f770b95df8e1beabd7417fc112190bc
Once the file has downloaded,copy to the root of your SD Card.
Open Mobile Uncle Tools and Select "Recovery Update".
Be sure to Select the downloaded recovery image,not anything else.
Select the file and proceed with installation.Mobile uncle tools will then prompt you to reboot into recovery if the update was successful.Select Yes and the phone will reboot into the new recovery menu
Credits to :
eddy.rugal - Base Rom
Carliv - For Recovery
njava - For Mobileuncle MTK Tool
Click to expand...
Click to collapse

any news on the kitkat rom yet? super excited to try this out!

is the link for the rom gone?
i dont see it

How to avoid TWRP Errors related to wrong Firmware for custom ROM & prepare FIRMWARE

How to avoid TWRP Errors related to wrong Firmware for custom ROM & prepare FIRMWARE
One of the most frequent question related to flash custom ROM is what firmware should I use to this particular ROM
That is probably because you had, or you would like to avoid ERROR 7 during flashing in TWRP which is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing
At the begging of flashing process updater-script check this:
Code:
getprop("ro.product.device") == "sagit" || abort("E3004: This package is for "sagit" devices; this is a "" + getprop("ro.product.device") + "".");
and trustzone
Code:
assert(sagit.verify_trustzone("TZ.BF.4.0.6-00124") == "1"); *
*(this version of TZ.BF is only example, I will describe that in the end)
Sometimes Developer allow to use wider TZBF like:
Code:
assert(sagit.verify_trustzone("TZ.BF.4.0.6-00124","TZ.BF.4.0.6-00130") == "1");
I assume that you fulfill the first condition (you have sagit, right?), so we will take to look deeper into second condition
How to know what trustzone is in the phone?
There are three methods:
1) when you lately flashed your phone with downloaded firmware or full miui rom (fastbooot or recovery) just unzip rom file (7-zip recommended) and look for tz.mbn file (see below)
2) Use app like Kernel Adiutor -> Statistics -> Device -> Trustzone (recommended method)
3) pull tz.mbn file directly from your phone
to do that you need adb tool, so under TWRP:
Code:
adb shell
cd /dev/block/bootdevice/by-name
ls -all
you should see list list of partition but what we looking for is that:
Code:
lrwxrwxrwx 1 root root 16 May 28 1970 tz -> /dev/block/sde15
copy partition to your storage
Code:
dd if=/dev/block/sde15 of=/sdcard/tz.img
now exit adb shell
Code:
exit
and copy tz.img to computer
Code:
adb pull /sdcard/tz.img
now we need hex editor to open tz.img or tz.mbn file
I use https://mh-nexus.de/en/hxd/ but you can your favorite hex editor
open tz file, press find and write TZ.BF, there is only one TZ.BF
QC_IMAGE_VERSION_STRING=TZ.BF.4.0.6-00124...IMAGE
Now, check what trust zone is needed in ROM which you would like to flash
It should be written in TrustZone requirements file named board-info.txt. It should be in github in root
In our case :
require version-trustzone=TZ.BF.4.0.6-00124
It's also written in your ROM file META-INF\com\google\android\updater-script
Despite of that you could use one of the firmware which have the same trustzone as needed I recommend that you follow firmware demanded/recommended by your ROM's Developer
version of TZBF in particular firmware:
8.2.2.0.NCAMIEC TZ.BF.4.0.6-00105
7.8.31 global TZ.BF.4.0.6-00124
7.8.31 china TZ.BF.4.0.6-00124
7.9.7 global TZ.BF.4.0.6-00124
7.9.8 china TZ.BF.4.0.6-00124
7.9.14 china TZ.BF.4.0.6-00124
7.9.22 global TZ.BF.4.0.6-00130
7.10.12 china TZ.BF.4.0.6-00130
7.10.12 global TZ.BF.4.0.6-00130
7.10.19 china TZ.BF.4.0.6-00130
China or Global?
In attached file.md5 there are md5sums of firmware files which I checked.
It seems, there is no difference between China or Global files from the same week (miui name ROM pattern version.mm.dd)
Do it at your Own Risk. I am not responsible for any loss or damage
EDIT 2017.11.14
Now its time to prepare your firmware based on XIAOMI ROM FILE
Choose version you need and download full ROM (not fastboot) from XIAOMI servers here
extract all files
go to extracted folder and delete all files/folders except folder firmware-update and META-INF
open META-INF/com and delete folder miui
download and extract updater-script from this tutorial
open \META-INF\com\google\android and repleace updater-script with this attached (mentioned above,downloaded and extracted)
Open it with eg notepad++ and correct /7.11.13 with version with you have and save it
go to main folder with firmware-update and META-INF and mark it, click righ mouse button and choose 7zip add to achrive
choose archive format zip, compression level store
copy to your phone and flash it with TWRP
that's it

Great information, thanks!
Following this information, I checked tz.mbn of xiaomi.eu rom 7.10.19. It provides firmware TZ.BF.4.0.6-00130.
Is this a correct conclusion? Or does the xiaomi.eu rom require TZ.BF.4.0.6-00130 and not provide it?

wian said:
Great information, thanks!
Following this information, I checked tz.mbn of xiaomi.eu rom 7.10.19. It provides firmware TZ.BF.4.0.6-00130.
Is this a correct conclusion? Or does the xiaomi.eu rom require TZ.BF.4.0.6-00130 and not provide it?
Click to expand...
Click to collapse
you dont have to worry about firmware in miui.eu ROM as they come with built in firmware,as stock MIUI ROM

deleted, double post, sorry

1. Flash my file: https://drive.google.com/open?id=1z9LbjzloH2Bjz-j8NfOc2e1-VImvMLIT
2. Wipe > format data > yes > enter > go back to main menu > reboot recovery
3. Flash your custom rom. Enjoy!

[ALE-L21] Debrick / Rebrand Package (C432 / B618)

Hi, I’ve created a flash package for the P8 Lite (2015) which I wanted to share with you.
DISCLAIMER:
I don't take responsbility for Bricked Devices or anything else.
The Linux Scripts are UNTESTED, use them only if you're really sure what you are doing.
Requirements are the following:
- A Windows / Linux (would recommend Debian / Ubuntu) PC
- A P8 Lite 2015 (ALE-L21) charged at least 50% and with unlocked bootloader
- A MicroUSB Cable
- A Hot Coffee or whatever do you drink
Instructions
1. Download the Package and extract it to an path without spaces
2. Make sure ADB and Fastboot are Installed
a. For Windows I recommend the 15 Seconds ADB & Fastboot Installer
Link to Thread
(Install System Wide)
b. For Linux: install the appropriate packages
3. Put your Device in Fastboot Mode OR enable USB-Debugging in Settings.
4. Run the corresponding script file (ADB = USB-Debugging / Fastboot = Fastboot Mode)
5. Drink your Coffee or whatever (and cross fingers)
6. Go to recovery and erase data.
7. Reboot your Device
Download Link: Here! (C432 CUST / BUILD B618)
Changelog:
v 1.0
Initial Release
Credits:
@worstenbrood for creating the Huawei Update Extractor
@Snoop05 for creating the 15 Seconds ADB and Fastboot installer
Redistribution:
You may link to this thread, no direct link please, so potential users read the instructions.
If the Package helped you, leave an thanks, that's all i'm asking for.

I get the belong bug B311.
Isnt B618 for dual sim anyway?

Yes, b617 is an option, for help with the extractor:
http://ministryofsolutions.com/2016/07/huawei-p8-lite-ale-l21-balongc52b311.html is a great tutorial for you.

Searching TWRP for the SM-A515F

Hi,
I would like install at the Samsung SM-A515F the Lineage OS and the TWRP. I found only TWRP for the SM-A50. And the flashing dose not work for this phone.
I has try it with Heimdall and Odin.
The recovery I had downloaed from this Page:
https://www.droidthunder.com/install-twrp-recovery-on-galaxy-a51/
Need help or better information, if there exist an TWRP and lineage for this device.
Regards tiptel170

No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page

sankhauaa said:
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
Click to expand...
Click to collapse
s 10 page? which one is that? can u please provide the link?

Go here for odin flash method without twrp

sankhauaa said:
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
Click to expand...
Click to collapse
sankhauaa said:
Go here for odin flash method without twrp
Click to expand...
Click to collapse
so does this method work for lineage os on A515F too?

After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.

ibtsam3301 said:
so does this method work for lineage os on A515F too?
Click to expand...
Click to collapse
I m not tried. But someone in this a51 group tried.Its working. But not so easy .
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
tiptel170 said:
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
Click to expand...
Click to collapse
Don't pay.Its fake

tiptel170 said:
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
Click to expand...
Click to collapse
of course it would be fake

How can I open the img-files in the Linux desktop?

Found here this link, for the Magisk in the A515F:
https://forum.xda-developers.com/ga...w-to-root-samsung-a51-sm-a515f-t4032389/page2

I'll found this:
1. https://www.androlite.com/2020/01/twrp-root-samsung-galaxy-a51.html
2. https://appslova.com/install-twrp-on-samsung-galaxy-a51/
This links look likes good, because, my phone will not start or the heimdall goes into the error (likes in de page one, the screenshots ).

I found this, and I used basic from this page: https://forum.xda-developers.com/showpost.php?p=82241115&postcount=70
My first steps to install the lineage os 17 on the SM-A515F
Lineage: https://sourceforge.net/projects/andyyan-gsi/
All commands in the linux terminal, the path please use your own paths you like it!
Unpack lineage****.xz:
unxz lineage*.xz
1) Extract the AP_file.tar.md5 from your firmware.zip file using 7zip
2) Extract the super.img.lz4 file from the AP_file.tar.md5 file using 7zip
3) Put super.img.lz4 file in LZ4 folder and run in CMD the command
lz4 -d super.img.lz4 superLZ4.img
4) Put superLZ4.img file in Simg2img folder and run in CMD the command
chmod 777 ~/bin/otatools/bin/simg2img
~/bin/otatools/bin/simg2img superLZ4.img superSIMG.img
In Linux OR Bash shell:
1) Put superSIMG.img in otatools/bin folder and extract it in Linux terminal using the command
chomd 777 ~/bin/otatools/bin/lpunpack
~/bin/otatools/bin/lpunpack --slot=0 superSIMG.img ~/1
2) Put, in the folder where you extracted superSIMG.img, the GSI file you downloaded and rename it to system.img. Now you should have odm.img, system.img, vendor.img and product.img files in the same folder.
You may also need to delete/remane the original system.img file before renaming the GSI file.
3) Now you’re going to make a brand new super.img file containing all 4 files of the previous step. This is a critical and tricky step. Run Linux terminal and type:
chomd 777 ~/bin/otatools/bin/lpmake
~/bin/otatools/bin/lpmake ~/bin/otatools/bin/lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:4294967296 --group main:4293513600 --partition system:readonly:1959841792:main --image system=./system.img --partition vendor:readonly:680239104:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
4) Make an tar file:
tar -H ustar -c super.img > lineageos17.1_SMA515F.tar
5) Goto Windows -> Odin -> AP, put the file lineageos17.1_SMA515F.tar in to the AP-slot -> Start
This is what I has done:
But, by the compiling, I got this error:
Code:
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition system will resize from 0 bytes to 1959841792 bytes
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition vendor will resize from 0 bytes to 680239104 bytes
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition odm will resize from 0 bytes to 4349952 bytes
Invalid sparse file format at header magic
Invalid sparse file format at header magic
And the phone is into the boot-loop, it will not starting the system.
Any help please...

Update:
System requirements:
- Fedora 32 with current kernel
- VirtualBox 6.1 with USB support
- Windows 7
- ODIN 3.14
Enable Root:
I) On mobile phone
1. carry out firmware update
1.1 Set up device, WITHOUT Google Accounts, WITHOUT security settings, set up WLAN only
1.2 Settings -> Phone info -> Software information -> Build number (press 7x )
1.3 Settings -> developer option -> enable OEM unlocking and USB debugging
2. copy the files from the root directory to the external SD card
2.1 Install MagiskManager
2.2 Starting MagiskManager
2.3 Installing Magisk Select
II) In the Fedora area
3. unpack the boot.img from the AP***.tar, on the PC
3.1 lz4 -d boot.img.lz4 boot.img
3.2 Copy the boot.img to the SD card from the phone
4. patching the boot.img in MagikMager
4.1 Select the boot.img, wait until "Done" appears.
4.2 Then copy the magisk_patch.img to the workstation (Fedora)
5.1 Rename the original boot.img to boot_original.img
5.2 renaming magisk_patch.img to boot.img
5.3 Transfer the new boot.img to the PC for the ODIN or HEIMDALL
5.4 Convert the boot.img to boot.tar: tar -H ustar -c boot.img > boot.tar (here for ODIN)
III) Virtual environment Win7
6.1 Copy the boot.tar from the Fedora workstation to the Odin directory of Win7
6.2 Open the boot.tar in the AP slot, Auto Reboot must be off
6.3 Press Vol + & Vol - simultaneously and plug in the USB cable (On SM-A515F), then click on "Start" in the ODIN.
IV) On the Mobile Phone
7.1 If ready, restart with Vol - & Hold PWR for more than 7 sec
7.2 Putting the device into recovery mode (switch off, press vol up and pwr simultaneously, Samsunglog appears, release pwr again)
7.3 Wipe your data: Wiped data/factury reset
Note: Device makes a boot loop for the first time - is normal. The first start takes quite long, be patient!
7.4 Settings -> Phone info -> Software information -> Build number (press 7x )
7.5 Settings -> Developer option -> Enable OEM unlock, USB debugging and system auto update to OFF
7.6 Installing and starting MagiskManger
The device will restart once!
Check it: Whether root is present
Fedora workstation:
Call Terminal, enter adb shell followed by su
If everything went well, the MagiskManager should answer the phone and ask for authorization.
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.

tiptel170 said:
Update:
System requirements:
- Fedora 32 with current kernel
- VirtualBox 6.1 with USB support
- Windows 7
- ODIN 3.14
Enable Root:
I) On mobile phone
1. carry out firmware update
1.1 Set up device, WITHOUT Google Accounts, WITHOUT security settings, set up WLAN only
1.2 Settings -> Phone info -> Software information -> Build number (press 7x )
1.3 Settings -> developer option -> enable OEM unlocking and USB debugging
2. copy the files from the root directory to the external SD card
2.1 Install MagiskManager
2.2 Starting MagiskManager
2.3 Installing Magisk Select
II) In the Fedora area
3. unpack the boot.img from the AP***.tar, on the PC
3.1 lz4 -d boot.img.lz4 boot.img
3.2 Copy the boot.img to the SD card from the phone
4. patching the boot.img in MagikMager
4.1 Select the boot.img, wait until "Done" appears.
4.2 Then copy the magisk_patch.img to the workstation (Fedora)
5.1 Rename the original boot.img to boot_original.img
5.2 renaming magisk_patch.img to boot.img
5.3 Transfer the new boot.img to the PC for the ODIN or HEIMDALL
5.4 Convert the boot.img to boot.tar: tar -H ustar -c boot.img > boot.tar (here for ODIN)
III) Virtual environment Win7
6.1 Copy the boot.tar from the Fedora workstation to the Odin directory of Win7
6.2 Open the boot.tar in the AP slot, Auto Reboot must be off
6.3 Press Vol + & Vol - simultaneously and plug in the USB cable (On SM-A515F), then click on "Start" in the ODIN.
IV) On the Mobile Phone
7.1 If ready, restart with Vol - & Hold PWR for more than 7 sec
7.2 Putting the device into recovery mode (switch off, press vol up and pwr simultaneously, Samsunglog appears, release pwr again)
7.3 Wipe your data: Wiped data/factury reset
Note: Device makes a boot loop for the first time - is normal. The first start takes quite long, be patient!
7.4 Settings -> Phone info -> Software information -> Build number (press 7x )
7.5 Settings -> Developer option -> Enable OEM unlock, USB debugging and system auto update to OFF
7.6 Installing and starting MagiskManger
The device will restart once!
Check it: Whether root is present
Fedora workstation:
Call Terminal, enter adb shell followed by su
If everything went well, the MagiskManager should answer the phone and ask for authorization.
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
Click to expand...
Click to collapse
It is work ???

GreggBorowski said:
It is work ???
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.

sankhauaa said:
I m not tried. But someone in this a51 group tried.Its working. But not so easy .
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
Don't pay.Its fake
Click to expand...
Click to collapse
sar please send me a51 group

Mehran` said:
sar please send me a51 group
Click to expand...
Click to collapse
Go to s10 page

sankhauaa said:
Go here for odin flash method without twrp
Click to expand...
Click to collapse
Not working. I has done step by step in this guide.

ibtsam3301 said:
so does this method work for lineage os on A515F too?
Click to expand...
Click to collapse
No. Withe manipulation from the vbmeta.img, the system is unwilling to start. It gos in to the bootloader, with error-codes. Like in first thread I describe. Olny the SAMSUNG original system works with the kernel modification for the MagiskManager.
I saw black for the future, there will be exist an custom rom for this device.

I have no idea, what can I do for this device. But I use and spend a lot of time for modification, without an good result. Has anyone an idea what can I do? But it look likes, it has an great secure system intern for not using an customer rom. This is my intention.