Database Info

[RADIO] HTC Desire's Family RIL Packages [15 SEP 2011]

Android's Radio Interface Layer (RIL) provides an abstraction layer between Android telephony services (android.telephony) and radio hardware. The RIL is radio agnostic, and includes support for Global System for Mobile communication (GSM)-based radios.
The RIL consists of two primary components:
RIL Daemon: The RIL daemon initializes the Vendor RIL, processes all communication from Android telephony services, and dispatches calls to the Vendor RIL as solicited commands.
Vendor RIL: The radio-specific Vendor RIL of ril.h that processes all communication with radio hardware and dispatches calls to the RIL Daemon (rild) through unsolicited commands.
There are two forms of communication that the RIL handles:
Solicited commands: Solicited commands originated by RIL lib, such as DIAL and HANGUP.
Unsolicited responses: Unsolicited responses that originate from the baseband, such as CALL_STATE_CHANGED and NEW_SMS.
Solicited
There are over sixty solicited commands grouped by the following families:
SIM PIN, IO, and IMSI/IMEI
Call status and handling (dial, answer, mute & hellip)
Network status query
Network setting (barring, forwarding, selection & hellip)
SMS
PDP connection
Power and reset
Supplementary Services
Vendor defined and support
The following diagram illustrates a solicited call in Android.
{
"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"
}
Unsolicited
The following snippet illustrates the interface for unsolicited commands:
There are over ten unsolicited commands grouped by the following families:
Network status changed
New SMS notify
New USSD notify
Signal strength or time changed
Informations collected from Netmite
Click to expand...
Click to collapse
The purpose of this topic is to provide a collection of extracted RIL for HTC Desire. I will add new one asap.
I try to test all these packages (too many Rom & config..it's quite difficult!) However note that flashing RIL files aren't dangerous at all for your phone. Just do Nandroid Backup!
You could share your own experience. I'll do my best to improve this collection!
Links:
[FROYO] HTC-RIL 2.2.0015HM (Aug 9 2010,11:40:11) (implemented with radio 32.44.00.32U_5.09.05.30_2, 32.46.00.32U_5.10.05.17_2 & 32.47.00.32U_5.10.05.23)
[FROYO] HTC-RIL 2.2.0025HM (Sep 9 2010,15:56:36) (implemented with radio 32.48.00.32U_5.11.05.14)
[FROYO] HTC-RIL 2.2.0028HM (Sep 20 2010,22:33:44) (implemented with radio 32.49.00.32U_5.11.05.27 & 32.54.00.32U_5.14.05.17)
[GINGERBREAD] HTC-RIL 2.2.0028HM (Sep 20 2010,22:33:44) (implemented with radio 32.56.00.32U_5.17.05.08)
[FROYO] HTC-RIL 2.2.0031HM (Sep 28 2010,23:02:55) (extracted from Desire HD Rom)
[GINGERBREAD] HTC-RIL 2.2.0035HM (Oct 12 2010,17:15:20) (extracted from Desire Z Rom)
[FROYO] HTC-RIL 2.2.0079HM (Jan 14 2011,14:56:03) (extracted from Desire HD Rom)
[GINGERBREAD] HTC-RIL 2.2.0098HM (Jan 27 2011,18:04:49) (extracted from Desire Z Rom)
[GINGERBREAD] HTC-RIL 2.2.0099HM (Jan 27 2011,16:12:49) (extracted from Desire HD Rom)
[GINGERBREAD] HTC-RIL 2.2.0121HM (Mar 11 2011,13:26:30) (extracted from Desire S Rom)
[GINGERBREAD] HTC-RIL 2.2.0131HM (Mar 18 2011,00:40:15) (extracted from Desire S Rom)
[GINGERBREAD] HTC-RIL 2.2.0143H (Mar 29 2011,15:29:57) (extracted from Desire HD Rom) (tks to kszaq)
HTC-RIL 1.6.1062G (Apr 23 2010,17:35:06)
HTC-RIL 2.2.0014G (Sep 24 2010,19:08:27)
HTC-RIL 2.2.0018G (Mar 24 2011,20:20:09) (tks to stony2k)
[GINGERBREAD] HTC-RIL 2.2.1001G (July 16 2010, 21:52:13) (extracted from N1 ROM)
[CRC32: 62FC7361 / MD5: 1D183306DF93BE525C33F92452232141 / SHA-1: 5238972645BEFA27EBDE6E25A3782D6E5BD8017A]
[GINGERBREAD] HTC-RIL 2.2.1003G (Nov 2 2010,17:17:45) (tks to adwinp for the release & System of a pWne!^ for the package)
Installation: (Tks to siedkins )
1. Reboot into recovery mode
2. Full nandroid back up
3. Select flash from SD card - select radio
4. Should get a notification to reboot to apply the radio flash
5. Once rebooted it will automatically take you back into recovery mode
6. Mount "/system"
7. Select flash from SD card - select RIL
8. Reboot once that has flashed and cross your fingers !!!
9. You could check HTC RIL version and compare with informations below with my little app (see attachment) or with ConnectBot:
Code:
su
getprop "gsm.version.ril-impl"
*** Please report any problem! ***
Note:
-Some radio update don't need to change the RIL!
-If you encounter some trouble, you could revert to your original RIL easily: just flash again your ROM or do a nandroid restore!
-RIL FILES ARE STORED IN ROM PART SO IF YOU WIPE & INSTALL ANOTHER ROM, PLEASE NOTE THAT NOTHING STAYS ON YOUR PHONE!
For testers:
If you want to help, you could send me your log:
1. Install Irssi ConnectBot (or the terminal application you prefer)
2. Launch the previous app and connect it (on Irssi, select "local" and give a name to the connection)
3. Then write these commands:
Code:
su
logcat>main_date.log (main log)
[I]or[/I] dmesg>kernel_date.log (kernel log)
[I]or[/I] logcat -b radio>/sdcard/radio_date.log (radio log)
[I]These 3 log will be very useful[/I]
4. Click on "home" button to keep your terminal launched
5. Do some tests with wifi, 3g, 2g connections (on/off), put the phone on sleep mode, on airplane mode...
6. When it's done, go back to your terminal and terminate the command with "ctrl+c" (on Irssi ConnectBot, just keep your finger on screen and a menu will appear with "ctrl+c")
7. You could exit your terminal
8. Your log should be on the root of your sdcard. Just make a post with your log attached or send me a pm!
HTC RIL Known Versions:
-GSM
Code:
HTC-RIL 2.2.0144HMQ (Mar 31 2011,11:44:35) / HTC Pyramid (Sensation)
HTC-RIL 2.2.0143H (Mar 29 2011,15:29:57) / HTC Desire HD (Ace)
HTC-RIL 2.2.0131HM (Mar 18 2011,00:40:15) / HTC Desire S (Saga)
HTC-RIL 2.2.0121HM (Mar 11 2011,13:26:30) / HTC Desire S (Saga)
HTC-RIL 2.2.0099HM (Jan 27 2011,16:12:49) / HTC Desire HD (Ace)
HTC-RIL 2.2.0098HM (Jan 27 2011,18:04:49) / HTC Desire Z (Vision)
HTC-RIL 2.2.0079HM (Jan 14 2011,14:56:03) / HTC Desire HD (Ace)
HTC-RIL 2.2.0048HM (Nov 17 2010,10:44:47) / HTC Desire HD (Ace)
HTC-RIL 2.2.0035HM (Oct 12 2010,17:15:20) / HTC Desire Z (Vision)
HTC-RIL 2.2.0031HM (Sep 28 2010,23:02:55) / HTC Desire HD (Ace)
HTC-RIL 2.2.0028HM (Sep 20 2010,22:33:44) / HTC Desire (Bravo)
HTC-RIL 2.2.0025HM (Sep 9 2010,15:56:36) / HTC Desire (Bravo)
HTC-RIL 2.2.0015HM (Aug 9 2010,11:40:11) / HTC Desire (Bravo)
HTC-RIL 2.2.1003G (Nov 2 2010,17:17:45)
HTC-RIL 2.2.1001G (July 16 2010, 21:52:13) / Nexus One (Passion) (Used by AOSP)
HTC-RIL 2.2.0018G (Mar 24 2011,20:20:09)
HTC-RIL 2.2.0014G (Sep 24 2010,19:08:27)
HTC-RIL 1.6.1062G (Apr 23 2010, 17:35:06) / Nexus One (Passion) (Used by AOSP)
-CDMA
Code:
HTC-RIL 2.0.0108H (Sep 20 2010,11:39:54) / HTC Desire CDMA (BravoC)
RIL Daemon:
Code:
To stop it:
su
stop ril-daemon
To start it:
su
start ril-daemon
RIL settings on build.prop:
Code:
ro.ril.a53.%s (gprs encryption algorithm)
ro.ril.3g.long.name
ro.ril.always.laccid
ro.ril.att.feature
ro.ril.avoid.pdp.overlap
ro.ril.def.agps.feature (network assisted gps)
ro.ril.def.agps.feature.%s (network assisted gps)
ro.ril.def.agps.mode (network assisted gps)
ro.ril.def.agps.mode.%s (network assisted gps)
ro.ril.disable.fastdormancy.is
ro.ril.disable.fd.plmn.prefix
ro.ril.disable.mcc.filter
ro.ril.disable.power.collapse (said to be an ultra-low power state when phone is in idle, saving battery) (so does =1 mean "yes, please disable the power collapse mode", and =0 mean "oh, please leave power collapse mode on")
ro.ril.ecc.%s
ro.ril.emc.mode
ro.ril.enable.3g.prefix (=1 shows "3g" on lock screen next to network name, =0 does not)
ro.ril.enable.a52
ro.ril.enable.a53
ro.ril.enable.amr.wideband
ro.ril.enable.cnap (Caller Name Presentation)
ro.ril.enable.dcm.feature
ro.ril.enable.dtm (Dual Transfer Mode)(ro.ril.enable.dtm : Only set this to 1 if your network allows simultaneous transfer of Circuit switched (CS) voice and Packet switched (PS) data over the same radio channel (ARFCN).
ro.ril.enable.ehplmn.feature
ro.ril.enable.enhance.nws
ro.ril.enable.enhance.search
ro.ril.enable.gea3 (gsm security algorithm)
ro.ril.enable.homezone
ro.ril.enable.hsdpaind
ro.ril.enable.hsupaind
ro.ril.enable.korea.stk (Korean Sim Tool Kit)
ro.ril.enable.kt.feature
ro.ril.enable.managed.roaming
ro.ril.enable.ncell.ind (neighboring cell)
ro.ril.enable.network_identify
ro.ril.enable.nitz (network informed time zone)
ro.ril.enable.pre.roam.network
ro.ril.enable.prl.recognition
ro.ril.enable.regucid
ro.ril.enable.sbm.feature
ro.ril.enable.sdr
ro.ril.enable.tim.feature
ro.ril.enable.ucsq
ro.ril.enable.vf.%s
ro.ril.enable.vt
ro.ril.enhance.htcdis
ro.ril.fast.dormancy.plmn
ro.ril.fast.dormancy.rule
ro.ril.fast.dormancy.timeout
ro.ril.fd.scroff.timeout
ro.ril.fd.scron.timeout
ro.ril.gprsclass:
[I] 2 : 3 slots : 8 - 12 kbps up / 16 - 24 kbps down
4 : 4 slots : 8 - 12 kbps up/ 24 - 36 kbps down
6 : 4 slots : 24 - 36 kbps up / 24 - 36 kbps down
8 : 5 slots : 8 - 12 kbps up / 32 - 40 kbps down
10 : 5 slots : 16 - 24 kbps up / 32 - 48 kbps down
12 : 5 slots : 32 - 48 kbps up / 32 - 48 kbps down[/I]
ro.ril.hsdpa.category (between 1 and 28)
ro.ril.hsupa.category (between 1 and 7)
ro.ril.hsxpa (0 - UMTS, 1 - HSDPA, 2 - HSDPA/HSUPA)
ro.ril.htcmaskw1
ro.ril.htcmaskw1.bitmask
ro.ril.last.radio.fatal
ro.ril.oem.ecclist (emergency call codes)
ro.ril.oem.mosms.mode
ro.ril.oem.nosim.ecclist (emergency call codes)
ro.ril.oem.show.act
ro.ril.pre.roam.id.list
ro.ril.pre.roam.name.list
ro.ril.qos.delivery.err.sdu
ro.ril.qos.delivery.order
ro.ril.qos.guarantee.dl
ro.ril.qos.guarantee.ul
ro.ril.qos.max.dl
ro.ril.qos.max.sdu
ro.ril.qos.max.ul
ro.ril.qos.maxpdps
ro.ril.qos.traffic.class
ro.ril.qos.traffic.priority
ro.ril.qos.transfer.delay
ro.ril.radio.svn
ro.ril.search.first.pnn
ro.ril.set.mtu1472
ro.ril.show.all.plmn
ro.ril.tim.feature
ro.ril.ucsq.mode
ro.ril.update.acoustic.table
ro.ril.vmail.%mcc
ro.ril.wp.feature
Informations collected from Cyanogenmod.com and extracted from libhtc_ril.so
2011-09-15 - Add HTC-RIL 2.2.0143H packaged by kszaq
2011-06-08 - Add HTC-RIL 2.2.0018G packaged by stony2k
2011-05-10 - Add HTC-RIL 2.2.1003G packaged by System of a pWne!^
2011-04-15 - Add HTC-RIL 2.2.0098HM from HTC Desire Z - Add info about Stock Rom i've used to extract packages
2011-04-14 - Add HTC-RIL 2.2.0028HM extracted from HTC Desire GB leak
2011-04-13 - Add HTC-RIL 2.2.0131HM from HTC Desire S (Tks to DomFel ), HTC-RIL 1.6.1062G & HTC-RIL 2.2.0014G
2011-03-22 - Add HTC-RIL 2.2.0121HM from HTC Desire S & HTC-RIL 2.2.0035HM from HTC Desire Z
2011-03-19 - Add all packages in Light Edition (all file, libs not directly related to RIL have been deleted)
2011-02-21 - Add "HTC RIL Known Versions" part
2011-02-19 - Add more infos about RIL & Update "Simple RIL Infos Displayer" (see attachment)
2011-02-06 - Update of all packages (error on updater-script!) / Add HTC RIL version for each package and the way to retrieve it
2011-01-22 - Add mirrors on Mediafire
2011-01-21 - Add list of RIL settings on "build.prop"
2011-01-20 - Packages updated with EDIFY scripting
2011-01-19 - Links actived iot obtain feedback
2011-01-09 - Add more informations about RIL
2011-01-07 - Add 32.44.00.32U_5.09.05.30_2_RIL.zip
2011-01-06 - Create the topic and add 32.47.00.32U_5.10.05.23_RIL.zip, 32.48.00.32U_5.11.05.14_RIL.zip & 32.49.00.32U_5.11.05.27_RIL.zip
Click to expand...
Click to collapse

Do you have the radio interface layer for 32.54.00.32U_5.14.05.17 ?
Thanks.

9600pro87 said:
Do you have the radio interface layer for 32.54.00.32U_5.14.05.17 ?
Thanks.
Click to expand...
Click to collapse
There are no change between RIL of 32.49.00.32U_5.11.05.27 & 32.54.00.32U_5.14.05.17 so you can flash 32.49.00.32U_5.11.05.27_RIL.zip

wow! seems so nice~try to flash now!

So what is the gain between 32.49.00.32U_5.11.05.27_RIL & 32.54.00.32U_5.14.05.17 ?
What is the point of this "new" (I'm not familiar with it though) type of radio ?

Sylde said:
So what is the gain between 32.49.00.32U_5.11.05.27_RIL & 32.54.00.32U_5.14.05.17 ?
What is the point of this "new" (I'm not familiar with it though) type of radio ?
Click to expand...
Click to collapse
I don't know the updates between radio 32.49.00.32U_5.11.05.27 & 32.54.00.32U_5.14.05.17 but the RIL (Radio Interface Layer) is "just" like drivers for the ROM so differents radio could have the same RIL.
You could read some informations about RIL here
To be sure i made MD5 sum between extracted RIL of this 2 radio, all files are exactly identicals.

zikyHD said:
There are no change between RIL of 32.49.00.32U_5.11.05.27 & 32.54.00.32U_5.14.05.17 so you can flash 32.49.00.32U_5.11.05.27_RIL.zip
Click to expand...
Click to collapse
Ok, thanks.

Ok I understand better what it is. I'll give a try on that.

zikyHD said:
A collection of extracted RIL for HTC Desire.
I have tested all these and confirm they all work.
Installation:
-flash the radio according to the instructions here
-just flash the correct *_RIL.zip from RECOVERY (all packages are signed)
Note:
-some radio update don't need to change the RIL!
*** Please report any problem! ***
32.49.00.32U_5.11.05.27_RIL.zip (works with 32.49.00.32U_5.11.05.27, 32.54.00.32U_5.14.05.17)
32.48.00.32U_5.11.05.14_RIL.zip (works with 32.48.00.32U_5.11.05.14)
32.47.00.32U_5.10.05.23_RIL.zip (works with 32.47.00.32U_5.10.05.23)
Click to expand...
Click to collapse
I think that I once read that RILs are only for stock ROMs. But as I can see you are using Oxygen and did try the RILs. So it is save to flash the RILs even if using Oxygen?

Is this usable with AOSP ROMs?

rikmer said:
I think that I once read that RILs are only for stock ROMs. But as I can see you are using Oxygen and did try the RILs. So it is save to flash the RILs even if using Oxygen?
Click to expand...
Click to collapse
the only difference i know between stock rom and custom rom about RIL:
on stock rom: you will find the RIL linked to the included radio.img
on custom rom: most of the time you will find the RIL of the radio.img recommended by the cooker
To answer your question, i flashed all these RIL on Oxygen and my phone is still alive

I'm getting an error while trying to flash the latest of these zips using CWM 3.0.0.5
Apparently amend update.zip format has been deprecated and they need to be moved to a new format.
From what I can tell these things just push a few files onto the /system partition so modifying the format would presumably be doable... I'm currently updating my housemates GSM Desire from stock to "rooted to the eyeballs" so I'll take a look later if I get a chance..

georgefrs said:
I'm getting an error while trying to flash the latest of these zips using CWM 3.0.0.5
Apparently amend update.zip format has been deprecated and they need to be moved to a new format.
From what I can tell these things just push a few files onto the /system partition so modifying the format would presumably be doable... I'm currently updating my housemates GSM Desire from stock to "rooted to the eyeballs" so I'll take a look later if I get a chance..
Click to expand...
Click to collapse
OK! Tks for your report. I flashed all packages with Amon_Ra's recovery v2 ...
I'm going to test with ClockworkMod Recovery 3.0.0.5!

zikyHD said:
the only difference i know between stock rom and custom rom about RIL:
on stock rom: you will find the RIL linked to the included radio.img
on custom rom: most of the time you will find the RIL of the radio.img recommended by the cooker
To answer your question, i flashed all these RIL on Oxygen and my phone is still alive
Click to expand...
Click to collapse
Hmm ... are you really sure? Just flashed the corresponding RIL for my radio and same thing as always happens. If I the screen is turned off and then enabled again connection is lost and wont return. Didn't you have the same problems? If yes how did you solve them?

ClockWorkMod 3.0.0.5 as 2.5.1.2 and 2.5.1.8 are non-official releases (not packaged by Koush)
I had 1 problem recurrent with 2.5.1.2 and 2.5.1.8 that I never had in 2.5.0.7
So I don't know if it's interesting to use those.

rikmer said:
Hmm ... are you really sure? Just flashed the corresponding RIL for my radio and same thing as always happens. If I the screen is turned off and then enabled again connection is lost and wont return. Didn't you have the same problems? If yes how did you solve them?
Click to expand...
Click to collapse
I have the same problems. Just recovered my Nandroid Backup and now stay on my "old" RIL.

georgefrs said:
I'm getting an error while trying to flash the latest of these zips using CWM 3.0.0.5
Apparently amend update.zip format has been deprecated and they need to be moved to a new format.
From what I can tell these things just push a few files onto the /system partition so modifying the format would presumably be doable... I'm currently updating my housemates GSM Desire from stock to "rooted to the eyeballs" so I'll take a look later if I get a chance..
Click to expand...
Click to collapse
I have seen the problem with CWM 3.0.0.5 and even if i agreed CWM dev, i think it's an important work to update all *.zip (mine but radio.zip too!!) Only to be accepted by one version of recovery...

rikmer said:
Hmm ... are you really sure? Just flashed the corresponding RIL for my radio and same thing as always happens. If I the screen is turned off and then enabled again connection is lost and wont return. Didn't you have the same problems? If yes how did you solve them?
Click to expand...
Click to collapse
I can confirm that. Oxygen 2.0 RC6 with the 05.27 Radio.
Sent from my HTC Desire using Tapatalk

rikmer said:
Hmm ... are you really sure? Just flashed the corresponding RIL for my radio and same thing as always happens. If I the screen is turned off and then enabled again connection is lost and wont return. Didn't you have the same problems? If yes how did you solve them?
Click to expand...
Click to collapse
I don't encounter this problem! If I have understood correctly, when you switch off/on your screen, you lost the connection ? What do you have to do to retreive the connection?

zikyHD said:
I don't encounter this problem! If I have understood correctly, when you switch off/on your screen, you lost the connection ? What do you have to do to retreive the connection?
Click to expand...
Click to collapse
I had to reboot to get connection back.
I already restored my nand so I dont know if airplane mode would have done the trick too but if I remember correctly it didn't the last time I flashed a RIL.

[VIDEO] First Look at Cincinnati Bell Official Froyo

Here it is:
http://www.youtube.com/watch?v=krAvfyQZX4o
Enjoy.

Thanks, we all love your videos. Looking forward to more!

Thanks man!

I looked over the internet and fount a msi file. Hopefully that's the official file.
I really appreciate your tutorial and letting us know such upgrade exist. By the time I have watched this tutorial, I have already installed KhalPower's SteelEpicBlueV4.
Thanks for sharing!

athlon866 said:
Is there a link to download?
Click to expand...
Click to collapse
It is in this thread back a few pages. Titled something like "It's Here...."

Stripped cbw.zip and current CinBell zip
Hi.
reverendkjr, did you modify the imgs in your stripped rom package? The cbw.zip linked in the youtube video isn't the same as the current cbw.zip found in Cincinnati Bell's xt720_files.zip. Or maybe they've updated their rom? I downloaded it today. md5sum successfully verifies both sets of files, but the sums are different between the zips.
*.md5 files from my cbw.zip:
Code:
3f28c64431c12075f8d1bcaae8f5ee51 boot.img
b54670747a8d8daeddc7eafee75c10f7 system.img
*.md5 files from reverendkjr's cbw.zip:
Code:
2c8a3b5452f9eddfa46217e61679d0d7 boot.img
7937a9c06a7d9794f3ba736ea21c7058 system.img
This is how I extract cbw.zip:
Code:
wget http :// www ultimobile net/XT720_Files/xt720_files.zip
7z e ACSetup.msi _883B25C497AFEB46BFAEB0A3A4F6A8FF
7z e _883B25C497AFEB46BFAEB0A3A4F6A8FF _BF775DB53FAC4E61B74E061A2095B331
mv _BF775DB53FAC4E61B74E061A2095B331 cbw.zip
I don't know how to open .img files, so I can't dig deeper.

Revs zip only contains nandroid image and a couple small things can't remember exactly, and the one from Cincinnati bell contains a whole bunch of crap, that's why theirs is like 3 times the size as revs.

pydave said:
I don't know how to open .img files, so I can't dig deeper.
Click to expand...
Click to collapse
That's quite interesting. FYI to extract .img files, use unyaffs. I think I saved the msi from the day they released it. If I can find it, I'll compare the sums.

pydave said:
Hi.
reverendkjr, did you modify the imgs in your stripped rom package? The cbw.zip linked in the youtube video isn't the same as the current cbw.zip found in Cincinnati Bell's xt720_files.zip. Or maybe they've updated their rom? I downloaded it today. md5sum successfully verifies both sets of files, but the sums are different between the zips.
*.md5 files from my cbw.zip:
Code:
3f28c64431c12075f8d1bcaae8f5ee51 boot.img
b54670747a8d8daeddc7eafee75c10f7 system.img
*.md5 files from reverendkjr's cbw.zip:
Code:
2c8a3b5452f9eddfa46217e61679d0d7 boot.img
7937a9c06a7d9794f3ba736ea21c7058 system.img
This is how I extract cbw.zip:
Code:
wget http :// www ultimobile net/XT720_Files/xt720_files.zip
7z e ACSetup.msi _883B25C497AFEB46BFAEB0A3A4F6A8FF
7z e _883B25C497AFEB46BFAEB0A3A4F6A8FF _BF775DB53FAC4E61B74E061A2095B331
mv _BF775DB53FAC4E61B74E061A2095B331 cbw.zip
I don't know how to open .img files, so I can't dig deeper.
Click to expand...
Click to collapse
CBW's has a flashing tool that makes it easier for someone who doesn't know what they are doing to flash it easier, it does the root and openrecovery steps automatic so that's why it's much bigger. We just use need the nandroid file here as we are mostly already rooted and have open recovery installed. In other words cbw package has training wheels lol

LibertyMonger said:
CBW's has a flashing tool that makes it easier for someone who doesn't know what they are doing to flash it easier, it does the root and openrecovery steps automatic so that's why it's much bigger. We just use need the nandroid file here as we are mostly already rooted and have open recovery installed. In other words cbw package has training wheels lol
Click to expand...
Click to collapse
pydave isn't saying the size is different. The files have changed.
md5sums compute identifying strings (i.e. 2c8a3b5452f9eddfa46217e61679d0d7) that can be used as fingerprints. If the md5sums are different, then the content of files is different. What pydave has found is that the nandroid files don't match what rev posted anymore. So, possibly ultimobile's modified or updated something. The md5sum of the system.img could easily have changed simply by rev making making a backup nandroid and posting it. But, there's no way we can change the boot.img because of the bootlock.
What's strange is that the md5 sum of the boot.img again doesn't match anything I've seen before and it's different from the first one that CBW shipped.
Code:
7e9aed3341102a79851d4d7a3286997b STR_U2_01.18.2/GAS_ASIA_USASHLSTBRTINT_P027/boot.img
eff22955e8e91eb19545a3af39973934 STR_U2_01.1E.0/GAS_EMEA_UCASHOTBRTLRTCEE_P001/boot.img
eff22955e8e91eb19545a3af39973934 STR_U2_01.1E.0/GAS_EMEA_UCASHOTBRTLRTGB_P021/boot.img
fb17ae0297d51862ca9804e22c6940f2 STR_U2_01.1E.2/GAS_ASIA_USASHLSTBSTARSG_P019/boot.img
e5b21dfe793c8116a02ec486fa867afc STR_U2_02.1E.0/GAS_EMEA_UCASHOTBRTLRTFR_P018/boot.img
e5b21dfe793c8116a02ec486fa867afc STR_U2_02.1E.0/GAS_EMEA_USASHOTBRTLRTIT_P001/boot.img
cc81052ecaac38c81e9c373806f8b6de STR_U2_03.20.1/GAS_ASIA_USASHLSTBRTRU_P012/boot.img
8e5d0e3b28d020dca7aed72d3811e8e9 STR_U2_04.1E.1/GAS_NA_NACBW_P011/boot.img
8e5d0e3b28d020dca7aed72d3811e8e9 STR_U2_04.1E.1/GAS_NA_NAREG_P011/boot.img
I'm going to see if I can find out some more about this kernel. I'm still looking for the msi I downloaded the day it was released by CBW to compare.

Mioze7Ae said:
pydave isn't saying the size is different. The files have changed.
md5sums compute identifying strings (i.e. 2c8a3b5452f9eddfa46217e61679d0d7) that can be used as fingerprints. If the md5sums are different, then the content of files is different. What pydave has found is that the nandroid files don't match what rev posted anymore. So, possibly ultimobile's modified or updated something. The md5sum of the system.img could easily have changed simply by rev making making a backup nandroid and posting it. But, there's no way we can change the boot.img because of the bootlock.
What's strange is that the md5 sum of the boot.img again doesn't match anything I've seen before and it's different from the first one that CBW shipped.
Code:
7e9aed3341102a79851d4d7a3286997b STR_U2_01.18.2/GAS_ASIA_USASHLSTBRTINT_P027/boot.img
eff22955e8e91eb19545a3af39973934 STR_U2_01.1E.0/GAS_EMEA_UCASHOTBRTLRTCEE_P001/boot.img
eff22955e8e91eb19545a3af39973934 STR_U2_01.1E.0/GAS_EMEA_UCASHOTBRTLRTGB_P021/boot.img
fb17ae0297d51862ca9804e22c6940f2 STR_U2_01.1E.2/GAS_ASIA_USASHLSTBSTARSG_P019/boot.img
e5b21dfe793c8116a02ec486fa867afc STR_U2_02.1E.0/GAS_EMEA_UCASHOTBRTLRTFR_P018/boot.img
e5b21dfe793c8116a02ec486fa867afc STR_U2_02.1E.0/GAS_EMEA_USASHOTBRTLRTIT_P001/boot.img
cc81052ecaac38c81e9c373806f8b6de STR_U2_03.20.1/GAS_ASIA_USASHLSTBRTRU_P012/boot.img
8e5d0e3b28d020dca7aed72d3811e8e9 STR_U2_04.1E.1/GAS_NA_NACBW_P011/boot.img
8e5d0e3b28d020dca7aed72d3811e8e9 STR_U2_04.1E.1/GAS_NA_NAREG_P011/boot.img
I'm going to see if I can find out some more about this kernel. I'm still looking for the msi I downloaded the day it was released by CBW to compare.
Click to expand...
Click to collapse
Are you looking fro CBs installation file (xt720_files.zip) or just the nandroid image?

3rdstring said:
Are you looking fro CBs installation file (xt720_files.zip) or just the nandroid image?
Click to expand...
Click to collapse
I was looking for xt720_files.zip. I found it. They are different, but I'm just starting to peel the skin. More soon.

Mioze7Ae said:
I was looking for xt720_files.zip. I found it. They are different, but I'm just starting to peel the skin. More soon.
Click to expand...
Click to collapse
Fudge. I just accidentally deleted it.
Anyway, the difference in the system.img is some new app called umFramework.apk (um presumably short for ultimobile).
The new kernel is:
3f28c64431c12075f8d1bcaae8f5ee51 boot.img
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 13 20:54:25 IST 2010
The previous one was:
2c8a3b5452f9eddfa46217e61679d0d7 boot.img
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Wed Jun 23 22:39:35 IST 2010
The other ones I've seen are:
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Thu May 27 16:17:00 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 13 17:19:35 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 13 17:19:35 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Thu Aug 5 16:27:41 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 13 20:54:25 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 13 20:54:25 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Wed Aug 4 22:22:08 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 20 01:36:37 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 20 01:36:37 IST 2010
So, the compile date and time matches the italian and french builds now but the md5sum doesn't.

Mioze7Ae said:
Anyway, the difference in the system.img is some new app called umFramework.apk (um presumably short for ultimobile).
Click to expand...
Click to collapse
Nobody install this attachment!
Now that's out of the way, can someone else look at the code (apktool) and tell me if it's doing what I think it's doing? My interpretation is it collects a bunch of information about the phone and SIM and uploads it to:
http://www.ultimobile.net/androidtracker/androidtracker/service1.asmx/Tracker
It may be harmless (or even beneficial for CBW users) so that CBW can do QA and monitor it's network quality. Dunno. See also:
http://www.ultimobile.net/androidtracker/androidtracker/default.aspx
In any case, I'm not sure I'd want this on my phone if I wasn't a CBW customer.

I decompiled with dex2jar and got the code from jd-gui.
Looks to me like it's doing what you described Mioze7Ae:
umFramework.apk contains a service that's started on boot. The service tries to upload some info and quits when upload completes (so it should only upload once per boot). Here's the Android documentation for what it's uploading.
getDeviceId: Returns the unique device ID, for example, the IMEI for GSM and the MEID or ESN for CDMA phones.
getDeviceSoftwareVersion: Returns the software version number for the device, for example, the IMEI/SV for GSM phones.
getSimOperator: Returns the MCC+MNC (mobile country code + mobile network code) of the provider of the SIM. 5 or 6 decimal digits.
Click to expand...
Click to collapse
I guess they watched reverendkjr's video and wanted to count the noncustomers who are flashing

My file was the original nandroid that they put out there with all of their crap added and instructions from the day it was released. I just yanked out the zip file and posted it elsewhere. It sounds to me like they have changed it after the fact.
Very interesting...

Hi Reverendkjr,
Thanks for all your videos. I have learned a lot from those videos.
I just want to know which ROM has a higher quandrant count: WanHu or CBW?
Thanks!

hermit_sim said:
Hi Reverendkjr,
Thanks for all your videos. I have learned a lot from those videos.
I just want to know which ROM has a higher quandrant count: WanHu or CBW?
Thanks!
Click to expand...
Click to collapse
+1 the videos from Rev help me a lot!
Same question for me, what is the best rom for XT720
Sorry for my bad english, I'm not English speaking

Hi all,
Same question for me, what is the best rom for XT720 in terms of stability?
Thank you

hermit_sim said:
Hi Reverendkjr,
Thanks for all your videos. I have learned a lot from those videos.
I just want to know which ROM has a higher quandrant count: WanHu or CBW?
Thanks!
Click to expand...
Click to collapse
I havent tried the CBW froyo but i am currently using the wanhu steelblue optimized and i have a quadrant score of around 1000 to 1100 when overclocked to 1000mhz 66vsel. But i have understood from other ppl in this forum that quadrant scores almost count for nothing and can be easily manupilated. (eg: increase read write speed of sd card, use memory optimizer for more RAM, etc...) hope that helps

[RESOLVED] changing baseband/unknown baseband/broken audio in calls

These steps are mainly directed at how to use the KDZ program to switch your baseband/fixing unknown baseband.
*I have heard this works on Windows Vista/7 but I personally have only been able to accomplish it through Windows XP*; VMWare running XP and XP Mode also work but make sure the USB is consistently being connected to the XP environment (don't jack around outside it) or the process will hang & require you to start over!*
1. You do NOT need to have stock recovery installed for this to work, it will require you to reflash CWM after though - How to NvFlash CWM Recovery
2. If you are not on a stock ROM prior to doing this your phone will get stuck in a boot loop of the stock T-Mobile animation when the process is finished; until you reflash CWM Recovery and restore a backup
Notes:
[While on a custom ROM and Recovery]
I have had the kdz method hang after the baseband flash but before installing the stock ROM & Recovery, leaving everything but the baseband unchanged; this could happen for you but I recommend making an Nandroid still if you care about losing your current data; similar log of how it will appear if this happens: Baseband flash hangup
[Modem causing process to hang]
The process may hang due to the LG Modem driver, disabling and re-enabling it should fix this (Start --> Run --> devmgmt.msc --> Modems --> LGE Android Platform USB Modem --> Disable/Enable)
Needed files:
T-Mobile G2x Android USB Driver - drivers so your computer recognizes phone
V11H_00.kdz | Mirror 1 - data for the June 05 2011 baseband (WIND MOBILE)
V21E_00.kdz | Mirror 1 | Mirror 2 - data for the July 15 2011 baseband
V21Y_00.kdz | Mirror 1 | Mirror 2 - data for the March 11 2012 baseband
KDZ_FW_UPD_EN - software to install the baseband
APX Drivers & NVFlash - driver and software to flash Clockwork Recovery on your phone again
P999 V10F Nandroid - Nandroid of stock 2.2.2/V10F ROM
P999 V21E Nandroid | Mirror 1 | Mirror 2 - Nandroid of the stock 2.3.3/V21E ROM
P999 V21Y Nandroid | Mirror 1 | Mirror 2 - Nandroid of the stock 2.3.4/V21Y ROM
LGMobile Support Tool - Checks if the LG ROM/Baseband is outdated
Call audio fix for V21E Baseband | Mirror 1 - Fix the audio issue during a call with the V21E baseband on a custom ROM
Call audio fix for V21Y Baseband | Mirror 1 - Fix the audio issue during a call with the V21Y baseband on a custom ROM (So you can still be on CM9 nightlies thanks to owain94)
If you're trying to update from the V21E/July 2011 baseband to the V21Y/March 2012 baseband you should only need the LGMobile Support Tool and be on a stock 2.3.3 ROM to get the new baseband.
Download whichever file(s) you need from above; if you've been crack flashing with your computer already you should only need the KDZ program & the V21E/V21Y baseband file
Install the G2X driver onto your computer
Extract the KDZ_FW_UPD_EN archive and right click the "msxml.msi" file and select Install
Next keep your finger held on the Volume Down button of your phone and connect the USB cable to the phone and computer and wait until your phone displays "S/W Upgrade; if your computer says it detected a device it needs a driver for extract the APX/NvFlash zip and navigate the computer to the APX folder for the driver"
Open the "KDZ_FW_UPD.exe" file and click the folder icon to locate the KDZ file
After you have navigated to the KDZ file select it and push "Launch software update"
The log will instantly show:
Code:
15:54:41 : Launching SW update
15:54:41 : Unpacking KDZ
*The program will hang for a minute or two while it is unpacking the file don't worry!*
After you will see some information similar to this:
Code:
15:54:51 : KDZ file extraced
15:55:08 : Files were extracted.
15:55:08 : LGMobileDL Load.
15:55:08 : Port = 4
15:55:08 : Connecting to phone
15:55:20 : Check Phone mode = 1
The program will pause again for a minute and then this will display:
Code:
15:55:57 : Phone type check.......
15:55:57 : LGMobileDL.DLL Loading....
15:55:57 : _SetAuthMark Fail
15:55:57 : AuthMark°¡ Á¤È®È÷ Phone¿¡ Write µÇÁö ¾Ê¾Ò½À´Ï´Ù!
15:55:57 : _SetAuthMark Fail
15:55:57 : LoadCDMAPhoneData() Error
15:55:57 : _DetachDLL Call
15:55:57 : _DetachDLL Call End
15:55:57 : Param : Path = C:\Documents and Settings\All Users\Application Data\LGMOBILEAX\Phone\V21E.wdb
15:55:57 : Param : moduleDir =
15:55:57 : Param : waitTime = 33000
15:55:57 : Param : UsbHighSpeed = 0
15:55:57 : Param : PhoneMode = 1
15:55:57 : Param : BinVersion = V21E_00
15:55:57 : Param : AuthMark = 0
15:55:57 : Call fn_StartUpgrade
Last you will hear your USB disconnect/reconnect multiple times while seeing this spammed; this will keep going until the value of "lParam = 100"
Code:
15:56:07 : CDMA: wParam = 2006, lParam = 0
15:56:07 : Model Dll Msg Not Found(2006, 0)
Once the program has reached 100 your phone will reboot displaying the LG Logo and after a few moments it will boot up running the chosen baseband.

About to do this (http://support.lgforum.com/lg/topics/t_mobile_g2x_update_for_sound_quality) to my phone, to update the baseband and in the name of science.
I'll let you know how it goes.
And then, I'll be flashing over RC3 because as per (http://forum.xda-developers.com/showthread.php?t=1679892) it works with the new baseband.
Wait about an hour or two and I'll have something posted.

Maybe...
http://forum.xda-developers.com/showthread.php?t=1287321
or...
http://forum.xda-developers.com/showthread.php?t=1619932

E: 5 Hours later I got it, back on July baseband and phones working, so happy ROFL

xBkKx said:
E: 5 Hours later I got it, back on July baseband and phones working, so happy ROFL
Click to expand...
Click to collapse
Yay! I use a VM of XP too...so much easier
Sent from my LG-P999 using Tapatalk 2

Gotta love XDA's finest. You guys make it hard to actually brick a phone. In the end there will always be a way out of a brick so long as we have XDA developers supporting the device I'm stuck at the S/W Upgrade screen from a failed baseband update using the LG tool and I'm trying this method now. My IParam is scrolling so I'm sure it's doing the job.
Booted and everything's great. It's unfortunate that I restored to a stock ROM and used the LG Tool which failed miserably before using this method instead. I thought this method took more work and look at that, for being hard-headed I ended up having to do more work than I would have had I just done it this way from the beginning.

Lucky me - my "new" replacement phone showed up and I went to work getting it all setup; rooted, ROM loaded, apps and settings - went to make a phone call and experienced what I am assuming to be "the "chirping" sound during a call" cited for the V21Y March 11, 2012 baseband. My settings verified the culprit baseband in question.
I am currently running through TGA_Gunnman's "NANDROID Restore Stock FR 2.22 V10f / GB 2.33 V21e and 2.34 V21y" tutorial to get back to stock and then unroot to follow this one. I am assuming I will need to use the "V21Y_00.kdz - data for the March 11 2012 baseband" but I'm bit unclear on how the "V21Y-BB.Fix.zip" plays into your instructions.
Any assistance would be greatly appreciated. - THX!

That bb fix zip is what owain made, just flash that to fix the chirping noise if you have it, it's so you can be on the new baseband and also a custom ROM
Sent from my LG-P999

That sounds good - I am running into trouble with the update however. I get all the way down through a bunch of the IParams till it hits this one -CDMA: wParam = 2010, IParam = 3035
Model Dll Msg Not Found(2010, 3035)​where it just hangs indefinitely. Tried it a few times and have a log saved if that would be of any help. I'm using an actual Windows XP machine (not a VM).
Thoughts?
Edit: Why do I get the sinking feeling I could have just flashed the BB fix to begin with? * sigh *

Is the USB connection staying connected? It disconnected around that on me sometimes and I had to retry, you could also try going into device manager and finding the LG Modem and disabling and re enabling it really quick (if the process hanged at a specific area during the Param spamming session longer than a minute it basically timed out, at least for me)
You said you were on the March baseband so why are you flashing it again? You need to V21E if you're switching. V21E July 15 2011/ V21Y March 11 2012 are the basebands.
You probably did just need to flash the bb fix zip that's why I mainly mentioned that :/ been at work so I'm sorry I haven't been able to be more clear
Sent from my LG-P999

Yeah - I ran the LG tool just to confirm my suspicions... guess I should have done that first. I did quite a bit of searching on the issue before deciding to nuke but didn't find the info spelled out for me (I'm still a rather "step by step" n00b, unfortunately)
It all works out though - The Eaglesblood ROM I was/am using updated since the version I installed Tuesday. It not only included the fix but a sweet install interface that did a lot of the leg work for me! - I am up and running great now! I used Titanium Backup Pro so the setup process wasn't quite so laborious.
Thanks for the help - and responses from work

When I'm doing this to get from 2.3.3 to 2.3.4 for the y21y BB the kdz update will get to the part where it says
15:56:07 : CDMA: wParam = 2006, lParam = 0
15:56:07 : Model Dll Msg Not Found(2006, 0)
But a few seconds later it will give me a runtime error.
Edit:
To be exact this is the full error.
Runtime Error!
Program: ...gs\administrator\desktop\stuff\kdz fw upd\kdz_fw_upd.exe
abnormal program termination
Edit2:
Decided to run VMware and windows xp on my desktop to see if it was just my laptop and lo behold it was something with my laptop.
It is currently installing and will come back to this if anything goes wrong or have in opinions.

Works fine for me. I just downgrade it to July baseband.
USB cable -> make sure you use the original cable from LG.
1st time flashing -> use Nokia cable -> failed -> stuck at Iparam=40++. (CWM is not removed). After reboot. The Phone Shows BB as July and bluetooth for car is working again. (So eventhough its stuck, the BB is already showing as July)
2nd time flashing -> use original LG cable -> works fine until Iparam=100. (CWM is removed when the program completed).
Thanks

I kept getting "mod uptestex mfc has stopped working" with vista. I needed to use VMware to run XP and then I was finally able to get it to downgrade to July 2011. Also once it gets to 100 you need to just unplug the phone because it will continue to bootloop until you install CWM and flash a rom or restore a nandroid. If you are doing this to get Bluetooth working in CM7.2 you will need to reflash 7.2 over your current 7.2 or you will have no call audio.

I am trying to flash v21y using the KDZ_FW_UPD tool
I am getting the error phone not found?
[R&D Test Tools Log File]
04:33:24 : Launching SW update
04:33:24 : Unpacking KDZ
04:33:35 : KDZ file extraced
04:33:38 : Files were extracted.
04:33:38 : LGMobileDL Load.
04:33:52 : Port = 0
04:34:06 : Connecting to phone
04:34:32 : PHONE WAS NOT FOUND!
04:34:34 : ===FINISHED===

vincy24 said:
I am trying to flash v21y using the KDZ_FW_UPD tool
I am getting the error phone not found?
Click to expand...
Click to collapse
In Device Manager under Modems make sure LGE Mobile USB Modem is enabled it will appear in there when the phone is connected and in the S/W Upgrade screen.
I tried this again on a fresh install of XP on my VMWare and it went fine..the KDZ Program should have "Type: CDMA" and "PhoneMode: DIAG" (should be default) as the options also, in case you messed with it.

solution here
http://forum.xda-developers.com/showthread.php?t=1619932
really works with unknown baseband

Dumb enough to get in trouble, smart enough to not make it worse
So, thought I was slick, I'm not, I'm a noob. Tmobile G2x in North America (Dallas, to be exact.) Was running 2.3.4 stock.
Downloaded & installed EAGLESBLOOD™ ICS AOSP [4.0.4]. Unfortunately, despite some thought of "was there a warning about this? I think I saw something somewhere" I did flash the baseband radio during the install.
Phone runs fine now, just have the dreaded click/thump noise and limited data. Can't make calls
Searched and found this thread. Looks like the cure but I'm unclear:
- Do I have to go back to stock (and if so, is there any concensus on which method to follow. I've seen several different threads)
- If I follow this thread, which files do I download/install? When I pull up "About Phone" I have baseband version M6600A-SCAUTNZ-2.0.9720T 1 [Mar 11 2012]
I'm sorry for my ignorance but I thought I'd ask before I install something and only make my problems worse.
Thanks,
Jeff

crosjn said:
So, thought I was slick, I'm not, I'm a noob. Tmobile G2x in North America (Dallas, to be exact.) Was running 2.3.4 stock.
Downloaded & installed EAGLESBLOOD™ ICS AOSP [4.0.4]. Unfortunately, despite some thought of "was there a warning about this? I think I saw something somewhere" I did flash the baseband radio during the install.
Phone runs fine now, just have the dreaded click/thump noise and limited data. Can't make calls
Searched and found this thread. Looks like the cure but I'm unclear:
- Do I have to go back to stock (and if so, is there any concensus on which method to follow. I've seen several different threads)
- If I follow this thread, which files do I download/install? When I pull up "About Phone" I have baseband version M6600A-SCAUTNZ-2.0.9720T 1 [Mar 11 2012]
I'm sorry for my ignorance but I thought I'd ask before I install something and only make my problems worse.
Thanks,
Jeff
Click to expand...
Click to collapse
Flash the rom again and when it gives you the option for baseband, click the 21y option. That'll fix the calling issue.
Sent from my LG-P999 using xda app-developers app

So awesome
Thanks, phone running muy bueno now. And who knew it was that easy to repair!
Many many thanks

[Completed] Elephone P7000 Wireless network update error!

Hi Guys,
Can someone help me with this?
2 Weeks ago I received my new Elephone P7000. Everything worked fine untill today.
I received a message on my phone that there was an official update for the wireless network …
It automatic doawnloaded this update after clicking on it and I was asked to reboot …
After the installation there was a message “Error!” so I pushed on the home and than the message was “No cammand!”
After pushing the home again I was in recovery mode. I backed up the personal userdatda via this menu and trieded to do a factory reset … I was wiping de personall userdata and the cache … nothing happens anymore … keeps rebooting in the main menu!
These are the errors after root integrity check:
Error:/system/app/Superuser.apk is new it is created on Thu Jan 1 00:00:00 1970
Error:/system/bin/su is new it is created on Thu Jan 1 00:00:00 1970
Error:/system/etc/install_recovery.sh is new it is created on Thu Jan 1 00:00:00 1970
Error:/system/xbin/su is new it is created on Thu Jan 1 00:00:00 1970
Error:/system/xbin/ksu.sud is new it is created on Thu Jan 1 00:00:00 1970
FAILED!
Kind Regards,
Luc Brossé

Hi there,
You'd be best served asking for help from the experts who own your device here:
P7000 Q&A, Help & Troubleshooting
Good luck

N920T Storage issues after flashing.

Greetings and salutations, fellow brothers and sisters in modding! You probably have never seen me around, but I've been here a looooong time, behind the scenes, clicking, watching, learning and, of course, modding it up like the crazy fool I am!
Let me just say I love XDA. XDA has helped me out of some HELLA messed up situations, a couple of times my reckless flashing has ended in bricking and if not for XDA I would have to do some fast talking! LOL
N e wayz!! My goal for this phone is to have a stable, updatable ROM on this phone. I need, at least, temporary root for sim unlocking later.
Right now, I'm very confused that after many hours of downloading and flashing the wrong firmware.... no, scratch that, I'm not confused at all.... this is exactly WHY my phone is doing what its doing...
I have root with cf-auto-root and I'm on firmware N920TUVS4DQA2_N920TTMB4DQA2_TMB
The rom is very stable but I only have 8gigs of total storage and the OS eats up about 7.5gigs of that so I can only install busybox and my storage is full!
The specs say I should have 32/64/128 GB of storage.
I'm not sure what to do next to fix this.
Also, I'm receiving a push notify, something about it being locked. I'll post a screen on it.
Any assistance is HUGELY appreciated!!!!!
Much love,
D
P.S. I have the Z3X unlock box for Samsung but it has done absolutely nothing with this phone except let me get the phone codes info off of it, so I'll copy/paste that in. Just in case it helps figure it out lol
Operation: Read Codes
Selected model: SM-N920T
Software version: 29.6
Waiting ADB device... OK
Reading phone info...
Model: SM-N920T
Android version: 6.0.1
Product code: SM-N920TZWATMB
Phone version: N920TUVS4DQA2
PDA version: N920TUVS4DQA2
CSC version: N920TTMB4DQA2
CSC country code: USA
CSC sales code: TMB
HW version: REV0.2
Phone SN: RF8G71W808R
Chip name: EXYNOS7420
Modem board: SHANNON333
Security patch: 2017-01-01
RF cal date: 20150728
IMEI: 000000000000000
Checking Super user right... true
Reading NV data... OK
Checking NV data... OK
Initialization zTool... OK
Running zTool, please wait... OK
HWID: 48 C6 12 AF 0E 07 00 00 00 00 00 00 00 00 00 00
Calculating... OK
Checking hash file... OK
Please wait, calculating codes... OK (time - 00:00:16)
Freeze code: 42050703
NET lock: 17368573
SUB lock: 00000000
SP lock: 00000000
CP lock: 00000000
SIM lock: 00000000
Done with Samsung Tool PRO v.29.6

Screenshot