Database Develop

How to flash CWM Recovery on Verizon Galaxy tab.

Hello, I just got a Rooted Verizon Galaxy Tab and I don't know how to flash clockworkmod recovery? I found what looks to be a great ICS rom at rootzwiki. However it need Clockworkmod recovery. Any ideas? All the links I find are dead, or no longer recommended. If you could point me in the right direction I would appreciate it. Thanks.
P.S. I looked at Verizon Tab Bootstrapper on the market but there are lots of people who experienced serious problems because of it. I'm not sure if they did it wrong or not. There is this one reviewer that says you need to be running the Original stock rom, maybe he means froyo? I can't seem to locate the original Froyo rom. Thanks.

you could start with
http://forum.xda-developers.com/showthread.php?t=1275031
that gets CWM 4.0 installed.

priyana said:
you could start with
http://forum.xda-developers.com/showthread.php?t=1275031
that gets CWM 4.0 installed.
Click to expand...
Click to collapse
That thread is for the Sprint version, would it work for the Verizon?
Also, I have a rooted stock rom installed. (or so I was told by the guy I got it from) But root checker basic says I don't have proper root access. Is that normal? Should I flash the absolute stock rom with Heimdall and do a superoneclick, rooting it myself?
Thanks.

I have a GSM device.
But I think verizon and sprint the same.
read his post. I don't think there is a superoneclick involved
If you read post #1, #2, then #3 you end up with root + CWM 4.0

priyana said:
I have a GSM device.
But I think verizon and sprint the same.
read his post. I don't think there is a superoneclick involved
If you read post #1, #2, then #3 you end up with root + CWM 4.0
Click to expand...
Click to collapse
Edit: I JUST DID IT!!! THANK YOU!!! I chanced it and used the ODIN I mention below to flash the custom kernel/custom recovery. I'm now doing a backup of the system! Next I'll flash the ICS Rom I found. THANKS!!! Also, I just realized I passed my 10th post! So Now I can post in the development threads! Thanks for that to!
Okay, also I can't seem to find ODIN for the Verizon version. I found ODIN3 v1.7 for the GT-P1000. Would that work for the Verizon version?
And he says to flash the Kernel with any EF17 installation? I don't understand. Thanks for your help.

Just follow the step. Basically, Odin flash the stock EF17 rom.
Then Odin flash the kernel that has CWM.
The Galaxy Tab doesn't have separate recovery.
Its recovery is included in the kernel. that is why you flash a kernel instead, to get CWM recovery.
And naturally you can't flash any kernel that has cwm, it has to be the one that is the same as the base kernel you already have.
BTW, his package has Odin included. you just really have to read carefully
Stock Odin/Heimdall Files: Stock EF17 Tar
Odin: Odin3_v1.7_SPH-P100 is included in tar package.
Heimdall: Homepage
The zip file below contains Odin3 v1.7, my .pit file, and full EF17 tar file including boot loaders and modem! There are no modifications or changes at all to the tar. Use this file to go back to a completely unrooted stock state. (Like you just did an OTA update)
Download stock-ef17-odin-tar-pkg.zip (Mirror) md5: b3f81ce371c3284882552cb22a38c29d

priyana said:
Just follow the step. Basically, Odin flash the stock EF17 rom.
Then Odin flash the kernel that has CWM.
The Galaxy Tab doesn't have separate recovery.
Its recovery is included in the kernel. that is why you flash a kernel instead, to get CWM recovery.
And naturally you can't flash any kernel that has cwm, it has to be the one that is the same as the base kernel you already have.
BTW, his package has Odin included. you just really have to read carefully
Stock Odin/Heimdall Files: Stock EF17 Tar
Odin: Odin3_v1.7_SPH-P100 is included in tar package.
Heimdall: Homepage
The zip file below contains Odin3 v1.7, my .pit file, and full EF17 tar file including boot loaders and modem! There are no modifications or changes at all to the tar. Use this file to go back to a completely unrooted stock state. (Like you just did an OTA update)
Download stock-ef17-odin-tar-pkg.zip (Mirror) md5: b3f81ce371c3284882552cb22a38c29d
Click to expand...
Click to collapse
Well, I flashed the custom kernel in odin and my System is still working. Although for some reason the computer wouldn't recognise the MicroSD so I had to use a reader. I rebooted into recovery and made a backup, then I wiped EVERYTHING (except SD card) and tried installing this: http://rootzwiki.com/topic/11697-rom-cdma-aosp-ics-cm9-build101-0418/ And its giving me:
Installing update...
assert failed: getprop("ro.product.device") == "galaxytab7c" | | getprop("ro.build.product") ==
"galaxytab7c" | | getprop("ro.product.device") == "plc" | | getprop("ro.build.product") ==
"plc" | | getprop("ro.product.device") == "SCH-I800" | | getprop("ro.build.product") == "
SCH-I800" | | getprop("ro.product.device") == "SPH-P100" | | getprop("ro.build.product") =
= "SPH-P100" | | getprop("ro.product.device") == "vzwtab" | | getprop("ro.build.product")
== "vzwtab
E:Error in /sdcard/(name of file).zip
(Status 7)
Installation aborted.
Any ideas? I'm doing a system restore now until I can figure it out. Someone on the thread did say we should be using CWM 5.3. I'm using 4. Where can I get 5.3?

common case for CWM 4.0 which if not mistaken can't do the assert
I don't know what you need to do to upgrade to CWM 5.0 first,
It is the best course of action if you can do it.
but there is other way,
can you use 7zip to open the zip, drag out from deep within the META-INF
there is an updater script
using wordpad, (not notepad) remove the part where it does the assert (the first few lines),
and drag the script back to the zip and flash it.
the end result, you get your cwm upgraded anyway because of the CM9/10

priyana said:
common case for CWM 4.0 which if not mistaken can't do the assert
I don't know what you need to do to upgrade to CWM 5.0 first,
It is the best course of action if you can do it.
but there is other way,
can you use 7zip to open the zip, drag out from deep within the META-INF
there is an updater script
using wordpad, (not notepad) remove the part where it does the assert (the first few lines),
and drag the script back to the zip and flash it.
the end result, you get your cwm upgraded anyway because of the CM9/10
Click to expand...
Click to collapse
Okay, first I'll try the newer official CM9.1 I found. And see if that works. If it doesn't then i'll try what you suggested. Thanks!

Electriccars said:
Okay, first I'll try the newer official CM9.1 I found. And see if that works. If it doesn't then i'll try what you suggested. Thanks!
Click to expand...
Click to collapse
Actually I am quite sure the latest cm gives the same error because you only have cwm 4
Sent from my GT-I9300 using xda app-developers app

priyana said:
Actually I am quite sure the latest cm gives the same error because you only have cwm 4
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Yeah it did. DOH! lol. Funny because I looked into the updater script of CM9.1 and didn't see the asserts lines. but I missed them. I am rezipping the file with the edited script and lets see what happens!

My reason of suggesting drag out and drag in is because sometimes rezipping screwed the zip in windows.
Windows is not Posix compliant, so if the filenames within are case sensitive, unzip and rezipping screwed it up.
Sent from my GT-I9300 using xda app-developers app

priyana said:
My reason of suggesting drag out and drag in is because sometimes rezipping screwed the zip in windows.
Windows is not Posix compliant, so if the filenames within are case sensitive, unzip and rezipping screwed it up.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Yeah. I only removed the specific file, changed it, deleted the old one, and inserted the edited one. I'm flashing it now...

Electriccars said:
Yeah. I only removed the specific file, changed it, deleted the old one, and inserted the edited one. I'm flashing it now...
Click to expand...
Click to collapse
Shoot, now it says:
E:Error in /sdcard/cm-9.1.0p1c.zip
(Status 6)
Installation aborted.
Any ideas?
Edit: Just found: http://forum.xda-developers.com/showthread.php?t=1585619
It says how to flash CWM 5. and flash ICS let me try that.

Did you use notepad?
The file is in Unix text, need wordpad.
Sent from my GT-I9300 using xda app-developers app

priyana said:
Did you use notepad?
The file is in Unix text, need wordpad.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
No I used wordpad. But no matter. I now have CM9.1 stable installed!!! With CWM 6! woohoo! Thank SO much for your help!

Tried several mods, don't get past logo's

I have a Samsung I9001 and I tried several mods. For example the
CM10.1 by ADC: http://forum.xda-developers.com/showthread.php?t=2315448
CM10.2 by ADC: http://forum.xda-developers.com/showthread.php?t=2436670
Mokee Open Source: http://forum.xda-developers.com/showthread.php?t=2425024
and AOKP: http://forum.xda-developers.com/showthread.php?t=2190224
I can format /data, /cache, /system, erase Dalvik cache, install zip's (In the CM mods, I have to delete the
Code:
assert(getprop("ro.product.device") == "ariesve" || getprop("ro.build.product") == "ariesve" ||
getprop("ro.product.device") == "GT-I9001" || getprop("ro.build.product") == "GT-I9001");
from the updater-script, or else I cannot install these mods. AOKP installs without a problem.
But when I boot these mods, they all get stuck at the CM booting logo or the "initiating swagger" logo of AOKP.
I tried installing factory mod of T-Mobile / Netherlands, it worked as expected. I could statup apps, call, sms, etcetera. After that installed AOKP, not passing logo. After that installed CM9 mod: http://forum.xda-developers.com/showthread.php?t=1650615. Not passing spinning CM logo....
I don't know what to do next.
What's missing? And what steps should I take now?

First off all there is no need to remove these lines from the updater-script.
To me its weird that your phone aint booting after installing the custom rom and mods you want.
Are you 1000% sure you have a i9001 and not a i9000?

mrjraider said:
First off all there is no need to remove these lines from the updater-script.
To me its weird that your phone aint booting after installing the custom rom and mods you want.
Are you 1000% sure you have a i9001 and not a i9000?
Click to expand...
Click to collapse
Well, I do have a i9001. I see it when I start the phone, behind the battery, on the package, so I don't think I accidentally think it's one.
I did install the CM9: http://forum.xda-developers.com/showthread.php?t=1650615
This one worked! (Still I had to delete those lines from the update script file)

Do you get some sort of error during flashing?

Some kind of patch for i9295 to use AOSP based 4.3 Roms

I was afraid to post this is Development Forum because it isn´t "Development" in any way. It´s the product of several hours of comparing others work, copy´n´paste, pack/unpack Roms and a lot(!) of frustration..
You may download, test, report and, most important, fix bugs of this. Pretty please!
You are using this at your own risk. I am in no way responsible for bricks...think twice before your doing anything.
What is he talking about ?
My Goal was to get i9505 4.3 AOSP based Roms working on our i9295.
Oh! What is working ?
- Display
- Hardware Keys
- Camera (Pictures)
Nice! What´s the Problem ?
- WLan is broken (I have no Idea) -- Medar has provided a fix here -- Thank you very much!
- Video recording (nope, no Idea)
I want to try, what do I have to do ?
- Download a i9505 AOSP based Rom (4.3 of course)
- Download the Patch
- Reboot into Recovery
- Wipe Data/Factory Reset
- Install the AOSP based Rom of your choice
- Install the Patch
- Wipe Cache, -> advanced- Wipe Dalvik Cache
- Install your Gapps
- Reboot into System
- Done!
--Optional
- Get angry about the bugs
- Fix them
- Tell us
I have tested this on Cyanogenmod "cm-10.2-20131206-NIGHTLY-jfltexx" build and SlimRoms "Slim-jfltexx-4.3.build.2.2-OFFICIAL-1762" build. But it should work on more Roms.
ALL Credits for this go to :
- LeJay for the initial unofficial CM Build
- spegelius for the more up-to-date CM Build
- Cyanogenmod
- WinMerge
- Notepad++
- My Wife for her Laptop
- and in advance to anybody working on a better Version/Bug Fixes

This is so nice I'll try it, new hope for ower active

Wow, i really like the idea behind this project! Thank you so much ohwarumbloss!
Gesendet von meinem GT-I9295 mit Tapatalk

considering the s4 GPE is getting 4.4.2 now... and we are trying to get 4.3 on our 4.2 device... I think this phone has been abandoned ... We are like 3 revisions behind.

Globel said:
considering the s4 GPE is getting 4.4.2 now... and we are trying to get 4.3 on our 4.2 device... I think this phone has been abandoned ... We are like 3 revisions behind.
Click to expand...
Click to collapse
Only 2 versions, and we're scheduled to receive 4.3 on December 24. I think the 4.3 to 4.4 has been a problem because Google released them not even 6 months apart from each other, so while companies were finalizing their 4.3 versions, they dropped 4.4.

mrmartin86 said:
Only 2 versions, and we're scheduled to receive 4.3 on December 24. I think the 4.3 to 4.4 has been a problem because Google released them not even 6 months apart from each other, so while companies were finalizing their 4.3 versions, they dropped 4.4.
Click to expand...
Click to collapse
Would you be kind and reveal the source of the scheduled update for S4 Active International? Thanks.

Globel said:
considering the s4 GPE is getting 4.4.2 now... and we are trying to get 4.3 on our 4.2 device... I think this phone has been abandoned ... We are like 3 revisions behind.
Click to expand...
Click to collapse
Never cared very much about Samsung. Or HTC ... Or whatever.
I have a full functional Cyanogenmod on my HTC Wildfire (4.3) which is really old
Spegelius' build of 4.3.1 10.2 is rock stable.
What we really need is a Developer who likes outdoor activities
Greetings
Thomas
PS: spend some days on building my own CM to learn but failed, yet. But Spegelius seems to be pretty successful so let's hope the best
Sent from my GT-I9295 using xda app-developers app

Hi
Using Slim-jfltexx-4.3.build.2.2-OFFICIAL, your patch and Camera JB+ I've manage to record 480,720 and 1080p videos with no lag. The only problem that I've found so far is no wifi conection. Thanks

medar said:
Would you be kind and reveal the source of the scheduled update for S4 Active International? Thanks.
Click to expand...
Click to collapse
Sorry, I was talking about the AT&T version. I neglected to remember that this was a i9295 thread. However, considering even AT&T is getting an update out, that means Samsung had to have done the legwork already to release an update sometime soon.

It would be cool if the patch can be developed to be used with any I9505 ROM on our I9295

Wifi fix for this patch
Flash this over recovery to fix wifi.
Don't forget to click thanks.

moviecut said:
Wow, i really like the idea behind this project! Thank you so much ohwarumbloss!
Gesendet von meinem GT-I9295 mit Tapatalk
Click to expand...
Click to collapse
Thanks
I like the fact that it seems to work, slowly, but we're getting activity for our active
medar said:
Using Slim-jfltexx-4.3.build.2.2-OFFICIAL, your patch and Camera JB+ I've manage to record 480,720 and 1080p videos with no lag. The only problem that I've found so far is no wifi conection. Thanks
Click to expand...
Click to collapse
Did you try the WiFi fix provided by medar?
gtchuah said:
It would be cool if the patch can be developed to be used with any I9505 ROM on our I9295
Click to expand...
Click to collapse
4.4 needs real Development but for 4.2 and 4.3 I think, there should be a way.
I don't use Sammy anymore, CM10.2 runs fantastic on my Device.
But, for 4.2 Sammy, you may start with a backed up boot.img from i9295 and restore it after you flashed i9505 Rom. There's nothing you can lose but a lot to win. And, don't we all need a Bootloop here and there, sometimes?
Seriously, worst case would be that you need Odin to flash a working recovery after a fail. Still, it's your own risk
medar said:
Flash this over recovery to fix wifi.
Don't forget to click thanks.
Click to expand...
Click to collapse
Awesome, thanks
Nice to see this!
Sent from my GT-I9295 using xda app-developers app

@ohwarumbloss: could you include a link to medar's fix in the original posting? Otherwise I fear people won't find it when the thread grows

pen² said:
@ohwarumbloss: could you include a link to medar's fix in the original posting? Otherwise I fear people won't find it when the thread grows
Click to expand...
Click to collapse
Yes, doing it right now

I am a fan of MIUI ROM. Coming to SGS4A, there is no porting of this MIUI ROM to SGS4A anymore.
This patch comes to my delight that there may be hope. Hence, with this patch, I'm planning to flash I9505's MIUI ROM (miuiandroid_multi_jfltexx_3.12.13_jb-4.2) to I9295 and flash the patch to see whether it works or not.
However, to my dismay, when I flash the MIUI ROM with CWM 1.2, I encountered the following messages:
assert(getprop("ro.product.device") == "jflte" ||
getprop("ro.build.product") == "jflte" ||
getprop("ro.product.device") == "jfltexx" || getprop("ro.build.product") == "jfltexx" ||
getprop("ro.product.device") == "i9505" || getprop("ro.build.product") == "i9505" ||
getprop("ro.product.device") == "GT-I9505" || getprop("ro.build.product") == "GT-I9505" ||
getprop("ro.product.device") == "jgedlte" || getprop("ro.build.product") == "jgedlte" ||
getprop("ro.product.device") == "i9505g" || getprop("ro.build.product") == "i9505g" ||
getprop("ro.product.device") == "GT-I9505G" || getprop("ro.build.product") == "GT-I9505G")
The installation aborted.
What should I do? Appreciate your expert advice.

hy
I am a fan of MIUI ROM too.. please post back if u made miui working on i9295 thx

Posted this to SlimRom forums: http://forum.slimroms.net/topic/100-galaxy-s4-active/?p=4479
Anyways, got a SlimRom build done and it seems to work. Merry christmas .

gtchuah said:
I am a fan of MIUI ROM. Coming to SGS4A, there is no porting of this MIUI ROM to SGS4A anymore.
This patch comes to my delight that there may be hope. Hence, with this patch, I'm planning to flash I9505's MIUI ROM (miuiandroid_multi_jfltexx_3.12.13_jb-4.2) to I9295 and flash the patch to see whether it works or not.
However, to my dismay, when I flash the MIUI ROM with CWM 1.2, I encountered the following messages:
assert(getprop("ro.product.device") == "jflte" ||
getprop("ro.build.product") == "jflte" ||
getprop("ro.product.device") == "jfltexx" || getprop("ro.build.product") == "jfltexx" ||
getprop("ro.product.device") == "i9505" || getprop("ro.build.product") == "i9505" ||
getprop("ro.product.device") == "GT-I9505" || getprop("ro.build.product") == "GT-I9505" ||
getprop("ro.product.device") == "jgedlte" || getprop("ro.build.product") == "jgedlte" ||
getprop("ro.product.device") == "i9505g" || getprop("ro.build.product") == "i9505g" ||
getprop("ro.product.device") == "GT-I9505G" || getprop("ro.build.product") == "GT-I9505G")
The installation aborted.
What should I do? Appreciate your expert advice.
Click to expand...
Click to collapse
Here´s what you need to do :
- get a tool like 7zip to unpack your downloaded Rom
- after you extracted it, navigate to /META-INF/com/google/android
- get Notepad++ and open the "updater-script"
- delete all lines that include "assert(getprop("ro.product.device") =="
- save the "updater-script"
- use 7zip (or similar) to include
Code:
[I] -META-INF
-system
-boot.img
-file_contexts (if there is such a file)[/I]
- into one .zip File again (like i.e. myrom.zip)
- Place your zip on your SD Card...reboot into recovery...do what you have to do
Don´t forget steps from opening Post, of course.
As always, you´re all alone with this, proceed with caution and at your own risk !!!
Good luck!
spegelius said:
Posted this to SlimRom forums: http://forum.slimroms.net/topic/100-galaxy-s4-active/?p=4479
Anyways, got a SlimRom build done and it seems to work. Merry christmas .
Click to expand...
Click to collapse
Can´t wait to try that out, this is great News !!! Going to be busy with da Family but maybe 26./27. of December I´ll be ready
Merry Christmas to you all

This is what I did from the beginning:
- Using Odin3 v3.07 to flash the original "I9295XXUBMK3"
- Using Odin3 v3.07 to root with "CF-Auto-Root-jflte-jfltexx-gti9505"
- Using Odin3 v3.07 to install "CWM-Recovery-gt-i9295_v1-2"
- Extract "miuiandroid_multi_jfltexx_3.12.13_jb-4.2" and open "\META-INF\com\google\android\updater-script" with Notepad
- Deleted "assert(getprop("ro.product.device") == "jflte".....till..... "GT-I9505G");"
- Re-zip "miuiandroid_multi_jfltexx_3.12.13_jb-4.2"
- Copy "miuiandroid_multi_jfltexx_3.12.13_jb-4.2.zip" and "patch.zip" to phone's root folder
- Reboot into Recovery
- Wipe Data/Factory Reset
- Wipe Dalvik Cache
- Install "miuiandroid_multi_jfltexx_3.12.13_jb-4.2.zip"
- Wipe Data/Factory Reset
- Wipe Dalvik Cache
- Install "patch.zip"
- Wipe Data/Factory Reset
- Wipe Dalvik Cache
- Reboot
During installation:
-- Installing: /sdcard/0/miuiandroid_multi_jfltexx_3.12.13_jb-4.2.zip
Finding update package...
Opening update package...
Installing update...
Formatting system...
Installing system files...
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete.
-- Installing: /sdcard/0/patch.zip
Finding update package...
Opening update package...
Installing update...
Flasing Patch
Flashing Boot Image...
Don t forget to wipe caches!
Install from sdcard complete."
When I reboot, it just stops at the startup screen, ie, "Samsun Galaxy S4 Active I-9295" indefinitely... no bootloop whatsoever.
What went wrong? And how do I rectify that?
Thanks a million for your help.

gtchuah said:
This is what I did from the beginning:
- Using Odin3 v3.07 to flash the original "I9295XXUBMK3"
- Using Odin3 v3.07 to root with "CF-Auto-Root-jflte-jfltexx-gti9505"
- Using Odin3 v3.07 to install "CWM-Recovery-gt-i9295_v1-2"
- Extract "miuiandroid_multi_jfltexx_3.12.13_jb-4.2" and open "\META-INF\com\google\android\updater-script" with Notepad
- Deleted "assert(getprop("ro.product.device") == "jflte".....till..... "GT-I9505G");"
- Re-zip "miuiandroid_multi_jfltexx_3.12.13_jb-4.2"
- Copy "miuiandroid_multi_jfltexx_3.12.13_jb-4.2.zip" and "patch.zip" to phone's root folder
- Reboot into Recovery
- Wipe Data/Factory Reset
- Wipe Dalvik Cache
- Install "miuiandroid_multi_jfltexx_3.12.13_jb-4.2.zip"
- Wipe Data/Factory Reset
- Wipe Dalvik Cache
- Install "patch.zip"
- Wipe Data/Factory Reset
- Wipe Dalvik Cache
- Reboot
During installation:
-- Installing: /sdcard/0/miuiandroid_multi_jfltexx_3.12.13_jb-4.2.zip
Finding update package...
Opening update package...
Installing update...
Formatting system...
Installing system files...
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete.
-- Installing: /sdcard/0/patch.zip
Finding update package...
Opening update package...
Installing update...
Flasing Patch
Flashing Boot Image...
Don t forget to wipe caches!
Install from sdcard complete."
When I reboot, it just stops at the startup screen, ie, "Samsun Galaxy S4 Active I-9295" indefinitely... no bootloop whatsoever.
What went wrong? And how do I rectify that?
Thanks a million for your help.
Click to expand...
Click to collapse
The Kernel inside the "Patch.zip" is a 4.3 Kernel.
But you try to use a Miui port based on a 4.2..
This means you need another Kernel.
One way could be to backup your Galaxy S4 active Sammy ROM after you flashed CWM recovery, then install the Miui port, go straight back to ->backup & restore ->advanced restore->choose your backup and restore "boot.img".
Then wipe cache & dalvik cache and reboot.
This may work, it should, but there is no guarantee.
Good luck
Sent from my GT-I9295 using xda app-developers app

How to port Lineage 13.0 (6.01) to XT907(and XT905)-JBBL and possibly others...

All the steps below are done at your OWN risk, and I take no responsibility blah blah blah
I will use explicit directory names and have referred to using Notepad++ and 7Zip. Both of which are free. But are not important to the actual process, just simplify the explanation for me. I will also be using Windows.
Both the above assumptions can be easily transferred to their UNIX or Mac equivalents.
1. Download the latest build from Lineage for the XT897
https://download.lineageos.org/xt897
2. Extract a copy of the file "/system/build.prop"
3. Open the build prop in a text editor
4. Do a global Find & Replace (case sensitive just to be sure)
xt897 to xt907
XT897 to XT907
5 Add and / or replace the following lines into the build prop (location in the file is not important, I personally add any new to the end and replace the values for existing)
Code:
ro.hdmi.enable=false
ro.cm.device=xt907
ro.product.device=RAZR M
ro.product.name=XT907
ro.build.product=scorpion_mini
ro.product.model=RAZR M
ro.boot.modelno=XT907
6. extract the attached vendor_motorola_xt907_proprietary.zip to C:\temp\xt907\
you should now have the directory structure of:
Code:
c:\temp\xt907\etc\firmware\
within the last directory should be two files
atmxt-r1.tdat
atmxt-r2.tdat
7. Add the etc\firmware directories at c:\temp\xt907\ to the zip, under the system directory.
you should now have within the zip
Code:
\system\
build.prop
\etc\firmware\
atmxt-r1.tdat
atmxt-r2.tdat
8. extract "\META-INF\com\google\android\updater-script" file from the zip to c:\temp\xt907\
9. Open the "c:\temp\xt907\updater-script" file in your text editor
NB: when editing this file, I would ensure that all line endings are "newline" not "CR-NL". In Notepad++ do a replace of "\r\n" with "\n"
10. Change the first line
FROM:
Code:
[COLOR="Red"][strike]assert(getprop("ro.product.device") == "xt897" || getprop("ro.build.product") == "xt897" || getprop("ro.product.device") == "asanti_c" || getprop("ro.build.product") == "asanti_c" || abort("This package is for device: xt897,asanti_c; this device is " + getprop("ro.product.device") + "."););[/strike][/COLOR]
TO:
Code:
[COLOR="SeaGreen"][B]assert(getprop("ro.product.device") == "moto_msm8960_jbbl" || getprop("ro.build.product") == "moto_msm8960_jbbl" || getprop("ro.product.device") == "xt907_jbbl" || getprop("ro.build.product") == "xt907_jbbl" || getprop("ro.product.device") == "xt901" || getprop("ro.build.product") == "xt901" || getprop("ro.product.device") == "solstice" || getprop("ro.build.product") == "solstice" || getprop("ro.product.device") == "xt905" || getprop("ro.build.product") == "xt905" || getprop("ro.product.device") == "smq_u" || getprop("ro.build.product") == "smq_u" || getprop("ro.product.device") == "scorpion_mini_u" || getprop("ro.build.product") == "scorpion_mini_u" || getprop("ro.product.device") == "XT907_JBBL" || getprop("ro.build.product") == "XT907_JBBL" ||getprop("ro.product.device") == "Moto Razr M" || getprop("ro.build.product") == "Moto Razr M" || getprop("ro.product.device") == "scorpion_mini" || getprop("ro.build.product") == "scorpion_mini" || abort("This package is for device: moto_msm8960_jbbl,xt901,solstice,xt905,smq_u,scorpion_mini_u,xt907_jbbl,scorpion_mini; this device is " + getprop("ro.product.device") + "."););[/B][/COLOR]
11. Add the following lines to the end of the updater-script file
Code:
ifelse(is_mounted("/system"), unmount("/system"));
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
package_extract_dir("system", "/system");
unmount("/system");
12. Save the file (take note of NL characters for line ending), & replace the one in the zip that you originally extracted it from ie "\META-INF\com\google\android\updater-script"
13. Rename the zip from something like "lineage-13.0-20170325-nightly-xt897-signed.zip" to "lineage-13.0-20170325-nightly-xt907-PORTED.zip"
14. reboot to TWRP
15. Make a backup!!!
16. Do a clean install and flash the appropriate GApps
17. Reboot & enjoy
Lineage do a weakly build for the XT897, and I think I previously use to dirty flash the ones I made. You can also see the change logs etc for the XT897 to know what to expect.
I have started to build my own XT905/XT907 ROMS from the source for the XT897, so it has been a while sionce I did the above, but I have modified the source to basically do the above steps. I actually still do the build prop file manually as its easier than modifying/maintaining the source. I also think you should be able to dirty flash it over an existing ZIP that was built using the above system.

Hi there. I've got a Razr M (XT907) that I used as my daily phone. It's currently running a nightly build of CyanogenMod 12.1 on Android Version 5.1.1.
Was looking through these instructions and two quick questions.
Main one -- I understand this post is a few months old, but this write-up seems to be for Lineage 13.0 whereas the newest version of the Lineage nightly is 14.1. Is that [significantly] relevant?
Also, "qtmxt-r1.tdat" and "qtmxt-r2.tdat" don't exist in my \etc\firmware directory, though an "atmxt-r1.tdat" and "atmxt-r2.tdat" do. Is that just a typo?
Kudos in advance!
-Dan

ProoN said:
Main one -- I understand this post is a few months old, but this write-up seems to be for Lineage 13.0 whereas the newest version of the Lineage nightly is 14.1. Is that [significantly] relevant?
Click to expand...
Click to collapse
I haven't explicitly checked, but the steps are the same. The only thing that may of changed is you should also search the build.prop for "asanti"/"asanti_c" or such and change to "scorpion_mini" and also check for "PHOTON Q" and change to "RAZR M". Also check that there are no duplicates of the build.prop's I added at the end.
I currently build my own LOS13 from source, so haven't performed the above since they switched to Nougat; maybe once when they first switched. Without the customisations of Xposed, LOS is to vanilla for me.
ProoN said:
Also, "qtmxt-r1.tdat" and "qtmxt-r2.tdat" don't exist in my \etc\firmware directory, though an "atmxt-r1.tdat" and "atmxt-r2.tdat" do. Is that just a typo
Click to expand...
Click to collapse
Typo corrected. thanks.
I also improved/updated step 11
And also realised the GAPPS should now be for 7.x

Alriiiiight. So, I've got the latest nightly build of Lineage OS, edited all files according to the instructions up there and am ready to *try* to install/flash this onto my device.
The XT907 is currently running a nightly build of CyanogenMod 12.1 on Android 5.1.1.
From how it sounds, I just need to boot into recovery (I've got TWRP) and install via micro SD, correct? It just installs atop CyanogenMod? I'm not really sure how it works.
This is my daily phone and I just don't want to mess anything up.

ProoN said:
Alriiiiight. So, I've got the latest nightly build of Lineage OS, edited all files according to the instructions up there and am ready to *try* to install/flash this onto my device.
The XT907 is currently running a nightly build of CyanogenMod 12.1 on Android 5.1.1.
From how it sounds, I just need to boot into recovery (I've got TWRP) and install via micro SD, correct? It just installs atop CyanogenMod? I'm not really sure how it works.
This is my daily phone and I just don't want to mess anything up.
Click to expand...
Click to collapse
What version of TWRP do you have? An older version wont be able to flash the latest ROMs
Are you running the JBBL?
1st you need to make a nandroid (ie BACKUP) of everything you have
Wipe cache, dalvik, data & system (you do not need to wipe internal SD)
Then flash the LineageOS zip file
Then flash the correct (ie same) version of GApps (I use OpenGapps pico personally) 7.x if you have latest LineageOS
Then flash your chosen method for root (optional, either Masgisk or SuperSU, I personally prefer Magisk but have not tested either with LOS 14.1 I run LOS 13.0)
Then reboot. Give it 10min to boot the first time.
If it fails, restore your backup.
Good luck.

I keep backups of all my data, generally once a week or so. Data loss on the device isn't a huge deal, I'm more concerned about the phone itself being inoperable once I [attempt to] flash Lineage onto it, lol.
My device is currently running TWRP v2.8.5.0. And if I remember correctly, any later versions of it wouldn't work for some reason -- I tried a few. Though, I haven't tried any other recovery programs as this version of TWRP worked fine for flashing CyanogenMod on here at the time (2015..)
Also, I'm not sure what JBBL is .. exactly.
Kudos for the quick replies though, much appreciated.

ProoN said:
I keep backups of all my data, generally once a week or so. Data loss on the device isn't a huge deal, I'm more concerned about the phone itself being inoperable once I [attempt to] flash Lineage onto it, lol.
Click to expand...
Click to collapse
If you take backups (nandroid and sdcard etc), this phone seems pretty safe to flash ROM zips through TWRP (but never say never... and it is possible if someone gives you a zip explicitly trying to kill your phone)
ProoN said:
My device is currently running TWRP v2.8.5.0. And if I remember correctly, any later versions of it wouldn't work for some reason -- I tried a few. Though, I haven't tried any other recovery programs as this version of TWRP worked fine for flashing CyanogenMod on here at the time (2015..)
Click to expand...
Click to collapse
I am pretty sure you will need to update TWRP again to flash these newer ROMs. For the latest see: https://forum.xda-developers.com/droid-razr-m/general/twrp-3-1-1-xt907jbbl-t3652141
ProoN said:
Also, I'm not sure what JBBL is .. exactly.
Click to expand...
Click to collapse
If you haven't taken the KitKat OTA or flashed the update manually, then chances you are on a JBBL (ie JellyBean Bootloader). Unless you bought the phone with KitKat pre-installed.

The phone was completely stock when I got it. There was a thread on here on how to unlock the bootloader, flash custom recoveries and OS's which is how I managed to get CM installed. How can I tell if JBBL is on here? Also, which version of Gapps would work for what I'm trying to do? (Lineage 14.1 on Android 5.1.1)
Sorry for so many questions. Kudos once again for the replies

ProoN said:
How can I tell if JBBL is on here?
Click to expand...
Click to collapse
"Settings > About phone > Kernel version" then search and read XDA ( eg https://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
https://forum.xda-developers.com/showthread.php?t=2226729
https://forum.xda-developers.com/showthread.php?t=2758398
https://forum.xda-developers.com/showthread.php?t=2345558)
ProoN said:
Also, which version of Gapps would work for what I'm trying to do? (Lineage 14.1 on Android 5.1.1)s
Click to expand...
Click to collapse
Lineage 14.1 is Nougat. Nougat is 7.X so you would get that (eg ARM, 7.1, PICO from open gapps)

Will flashing Lineage OS on here update the Android system entirely from 5.1.1 to 7.x.x? I guess that's my main confusion here.

ProoN said:
Will flashing Lineage OS on here update the Android system entirely from 5.1.1 to 7.x.x? I guess that's my main confusion here.
Click to expand...
Click to collapse
You are OT,best to ask your question here https://forum.xda-developers.com/showthread.php?t=2259645

Alright. So here's a not-so-newbie question. I went ahead and updated TWRP from v2.8.5.0 to v3.1.1-0 -- it was on another thread you had posted (the JBBL version seems to work on mine.)
Instead of trying to flash Lineage 14.1, I went along with the instructions for 13.0, edited the files and parameters accordingly, booted into TWRP and tried to install via zip and am getting this error
"Invalid zip file format!"
"Error installing zip file '/sdcard/lineage-13.zip"
Also have a copy of the zip file on the external_sd which reports the same error. I've tried this on both Windows and OSX with different zip programs and get the same error. Not sure what's happening here.

ProoN said:
Also have a copy of the zip file on the external_sd which reports the same error. I've tried this on both Windows and OSX with different zip programs and get the same error. Not sure what's happening here.
Click to expand...
Click to collapse
So, clearly your zip file is corrupted by your doing/zip application, not the actual steps I have above. I personally use 7Zip (freeware), and have had no corrupted zips issues. And it actually is a pretty newbie question If you want help, put the actual TWRP log up here, what you have posted tells us nothing.

Alright, making progress here. ..kind of.
I was originally extracting the archive entirely, editing and moving where necessary and then re-zipping. I'm not entirely sure why that method doesn't work when trying to install, but it doesn't.
So yeah. I've got TWRP 3.1.1-0 on my device now (JBBL version.) I followed the steps above as far as I'm aware but am getting a different error now.
{
"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 used Notepad++ as well, though there wasn't a single instance of \r\n that was replaced when following the instructions

ProoN said:
Alright, making progress here. ..kind of.
I was originally extracting the archive entirely, editing and moving where necessary and then re-zipping. I'm not entirely sure why that method doesn't work when trying to install, but it doesn't.
So yeah. I've got TWRP 3.1.1-0 on my device now (JBBL version.) I followed the steps above as far as I'm aware but am getting a different error now.
[SCREENSHOT]Sheeze! a link to the image or a little bit of a trim may of been in order. There is actually a feature under "Advanced" (I think) to copy the log to your SDCard (ie as text)
Click to expand...
Click to collapse
The line "This package is for devices with a 4.1 bootloader" is basically telling you that you do not have a JBBL. ie you have a KKBL.
JBBL=4.1
KKBL=4.4.2
If you search these forums, there have been recent posts regarding installation zips (ie flashable) that can switch you back and forth between JBBL and KKBL for an xt907. eg https://forum.xda-developers.com/showpost.php?p=73317190&postcount=13

ProoN said:
I was originally extracting the archive entirely, editing and moving where necessary and then re-zipping. I'm not entirely sure why that method doesn't work when trying to install, but it doesn't.
Click to expand...
Click to collapse
FYI: some of the reasons it could fail include (but are not limited to): Re-ziping can change the compression method (ie from simple STORE to compressed) and the zip file may (I dont think this one does) include some files which are case sensitive, while if re-zipped on Windows, chances are you are not on a case sensitive file system.

I did a quick look over...but I might have missed it. Does any of this required an unlocked bootloader? Mine is currently locked.

DragonFire1024 said:
I did a quick look over...but I might have missed it. Does any of this required an unlocked bootloader? Mine is currently locked.
Click to expand...
Click to collapse
Look, read and think. The answer is staring you in the face.

Is there any chance you could upload a copy of the zip you managed to port to the XT907? I've tried this several times on XP and Windows 7 with WinRAR and 7Zip. I can't get it to work at all.

ProoN said:
Is there any chance you could upload a copy of the zip you managed to port to the XT907? I've tried this several times on XP and Windows 7 with WinRAR and 7Zip. I can't get it to work at all.
Click to expand...
Click to collapse
are you talking MM or N? Are you getting errors in TWRP? if so, what? and please dont post a screen shot/photo, copy the log in TWRP to your SD (an option in twrp) and post the text

p20 pro unlocked bootloader with Lineage os 16.0

UPDATE: Please read my last message as that is where i am now. stuck on ERROR 7 while trying to sideload Latest Lineage Rom in twrp 3.3.0.2
hello People of Xda i have a question i just bought a p20 pro with unlocked bootloader and it is running los 16.0 long story short i bought this phone with unlocked bootloader and how it is now
p20 pro
Serial Number: LCL0218320009805 (its a CLT-09 apearently)
Build Number: lineage_charlotte-userdebug 9 PQ3A. 190705.003 e6b2c9a74b witch is the lineage-16.0-20190722-nightly-charlotte- i think
sha256
but i have a few questions i just wanna install magisk on it but i read there are a few restrictions that i couldnt just flash trough twrp but i have to sideload and flash apps because of encryption or something i dont fully understand that.
so what i want done sideloaded open gapps that worked and then rebooted everything worked fine.
p20 pro
Serial Number: LCL0218320009805 (its a CLT-09 apearently)
Build Number: lineage_charlotte-userdebug 9 PQ3A. 190705.003 e6b2c9a74b witch is the lineage-16.0-20190722-nightly-charlotte- i think
sha256
if i press Volume up + Power when phone is off it boots me to Erecovery but when i use this tool https://forum.xda-developers.com/hu...l-one-driversunlocktwrpfactory-t3779416/page5 And click Reboot Recovery while android is running it reboots me into Twrp 3.3.1-0 but i dont know whatbuild official or an unoffical. i tried to make a backup in twrp but it says can not create /data/media/0/TWRP Folder (required key not available) failed to make backup folder.
So i looked at the folders but when i look into my /sdcard it shows 10 maps with names like (2XtndypQA4RQ0dCtNechaB) and (BvZw1HkIUW5LDKk4BJgNSB) and 8 more so the guy told me i should sideload the open gapps and magisk trough that ALL in One Tool but when i do it says the same error as when i want to make a backup
it also says Failed to mount /system_root aprearently this is the encryption that i can`t turn off off on the phone.
on all my other rooted phones its not this much of a hassle and i dont want to break anything by doing something that I cant undo I`d rather ask some experienced people.
EDIT:UPDATE
I lost my Twrp because i sideloaded magisk 19.3 and flashing latest offical twrp to recovery didn`t work. i think because of magisk somehow.
This Guide says https://www.xda-developers.com/how-to-root-the-huawei-p20-pro-and-install-magisk/ i have to do that but its for CL29 and i do own a CL29 but the bootloader is locked on that device thats why i bought a second p20 pro xD so maby someone can kick me in the right direction on how to go on from this or had experience doing this. or is that guide outdated and can i just install magisk now
so what i dont know if i should do is
A: Rebrand the phone to CLT-29 to install that boot img for magisk (i dont know if that removes the unlocked bootloader) depends on what method i use i think? and if i need to downgrade first
B:downgrade back to a 8.1 stock rom first but i dont know my what my stock firmware is and firmware checker doesnt work because of los 16.0
C:i just want magisk but i dont know for sure if i can just flash magisk on my current build and still be able to hide root in magisk because apearently that is a problem (something with decrypting in Twpr)
D: i dont know if i can just not flash stuff on this twpr build or if its perfectly fine on the unofficial build i think he used https://forum.xda-developers.com/hu...awei-p20-pro-charlotte-l29c432b131-8-t3809964 this twpr build
honestly im finding it allot of info to take in and im lost on what to do now as i didnt root the phone myself and didnt really know what happened and what i can and cannot do safely.
I don`t know what information is outdated for my latest build and and im comming into the P20 scene fairly late can someone give me a hint on what to look out for trying Magisk and twrp to work on my build.
i just dont wanna lose my boot loader unlock or full brick the device and i feel im so close xD

ok it starts to make more sense now i think im on a official twrp 3.3.1-0 that does not decrypt my files thats why i got all these wierd folders
I don`t think I need to rebrand i can just go back to 8.1 maby with this guide ? https://www.getdroidtips.com/downgrade-huawei-p20-pro-android-pie-oreo/#Instructions (doesn't remove bootloader unlock right?)
and then install https://forum.xda-develop...ery-twrp-3-2-1-0-t3769917 so im decrypted and the wipe system and data should work normally right? and i can just start flashing trough twrp like i normally do because this all throws me off a little
and then i can install a modded boot image to make magisk work that works both on cl29 and my c09
i found a site that has my stock rom i need https://www.allrom.ir/2018/04/04/رام-فارسی-اندروید-8-0-هوآوی-پی-20-پرو-clt-l29-l09/
thats the firmware i need its the same as in the 8.1.0.106 (C185) for CLT_L29 / L09 the only problem is they sell it for 1500$ and im far from being that rich ;p
All help tips and tricks would be greatly apreciated if you need more info im more then willing to provide i dont wanna give up on my phone i know it`s possible somehow!
Screenshots:
Root Checker Safteynet check and About Phone >
https://ibb.co/XDZSFXh https://i.ibb.co/yFzp8Fz/Screenshot-20190724-082956-Root-Checker.png https://ibb.co/0mHG6Gp

Okay After i got everything working and know how to get Magisk working i need to fix my google play services so i thought lets reflash the lineage 16.0 latest rom and Mind The Gapps but everytime i try to sideload the Rom trough Twrp i get Updater process ended with ERROR: 7
or ' /sideload/package.zip
E3000:this package expects the value " _a" for "ro.
boot.slot_suffix";
im using adb push lineage-16.0-20190723-nightly-charlotte-signed.zip /tmp/ and i tried adb sideload lineage-16.0-20190723-nightly-charlotte-signed.zip
any tips?
tried to wipe system and cache before flashing but now i ended up with no OS on my phone xD my gawd twrp Works and Bootloader works so i should be good.
do i need to remove lines from the updater script of the lineage-16.0-20190723-nightly-charlotte-signed.zip ?
Luk said 'boot.img'; 'slot_suffix'. so i looked them up and it should be line 4 and 25 so do i remove those whole lines of code that i selected in red?
This is the code:
1. assert(getprop("ro.product.device") == "charlotte" || getprop("ro.build.product") == "charlotte" ||
2. getprop("ro.product.device") == "kirin970" || getprop("ro.build.product") == "kirin970" || abort("E3004: This package is for device: charlotte,kirin970; this device is " + getprop("ro.product.device") + ".");
3. assert(huawei.verify_vendor_build_id("P") == "1");
4. getprop("ro.boot.slot_suffix") == "_a" || abort("E3000: This package expects the value "_a" for "ro.boot.slot_suffix"; this has value "" + getprop("ro.boot.slot_suffix") + "".");
ui_print("Target: Huawei/lineage_charlotte/charlotte:9/PQ3A.190705.003/e6b2c9a74b:userdebug/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup", "/system/system");
unmount("/system");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
run_program("/sbin/e2fsck", "-fy", "/dev/block/bootdevice/by-name/system");
run_program("/tmp/install/bin/resize2fs_static", "/dev/block/bootdevice/by-name/system");
run_program("/sbin/e2fsck", "-fy", "/dev/block/bootdevice/by-name/system");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore", "/system/system");
unmount("/system");
show_progress(0.050000, 5);
25. package_extract_file("boot.img", "/dev/block/bootdevice/by-name/kernel");
show_progress(0.200000, 10);
set_progress(1.000000);

#Last Post Everything works now and im happy Thanks to Luk who gave me a nudge in the right direction. Luk said 'boot.img'; 'slot_suffix' I said thank you ;'p
Im gonna leave this post so others can learn from my mistakes.... If you have any questions about any of the things in my thread go ahead im basicly Pro now ;P