Related
Got a CNM 9DC Touchpad a few days ago and noticed there was a newer firmware online via the CNM website. Flashed it, flash went ok but when i turned the tablet on it displays a white only screen. Have spent various hours messing about with it since then, resetting, flashing different firmwares etc with no joy. I didn't save the original firmware before flashing it (schoolboy error!).
The only firmware i have found to semi work is the firmware for the 7DC but the screen is far too stretched due to the size difference so therefore unusable but at least i know the tablet isn't completely bricked. Tried emailing CNM but have had no reply so far. Anyone know where i could find the original firmware or how i could solve the problem? :good:
Anyone?
Got the same problem, did you every sort it?
CNM 9DC
Same here happened to me over a week ago. got 2 for my kids at xmas. i wanted to root them and found a website which had rooted versions for 7dc 9dc and 10.1dc. wanting to play it safe i made sure i had download the firmware from the cnm website so i could flash back if there were an problems. with the rooted one i was left with a white screen and it was no better with the cnm firmware. it is working as i get a display using hdmi and im able to control it using a mouse. i do still have one of the tablets with the firmware on which if i could just copy it off would sort the problem im sure but havent a clue how to. i also emailed cnm and got the following in reply.
“All the fir mare we have available is on our website, we do not have any other versions for the 9DC.
Richard Michael Hawes and Matthew David Smith were appointed Joint Administrators of KMS Components Limited (the “Company”) on 8 January 2014. The affairs, business and property of the Company are being managed by the Joint Administrators. The Joint Administrators act as agents of the Company only and contract without personal liability. The Joint Administrators are authorised by the Institute of Chartered Accountants in England and Wales (ICAEW). All licensed Insolvency Practitioners of Deloitte LLP are licensed in the UK.
As a result of the administration we are no longer able to provide a repair or replacement service. In the first instance we recommend that you return your tablet to the retail outlet from whom you purchased the tablet. If they are unable to offer you a replacement or a refund and you feel you have a valid warranty claim, you are entitled to register a claim as an unsecured creditor for the value of the purchase. In order to do this, please visit and download the Notification of Creditors letter. A copy of your receipt must be submitted with your proof of debt form.
If your tablet is out of warranty you will not be able to make a claim.
Apologies for any inconvenience this may cause.”
the rooted firmwares i got from here blog*zackehh*com/cnm-touchpad-modified-firmware-images
Life saver, there is a bit of software you can use to get a flash able back-up from, just need to find the link for it now.
http://www.freaktab.com/showthread....your-RK-device-(ROM)-with-the-new-RK-2-1-tool this is the one, there is a read me file, let me know how you get on.
If you manage to get the image then if possible could you please make it available somewhere. I have the exact same problem, but don't have a second one to get an image from. I also feel sure that there are quite a few others out here that would be extremely grateful.If what I have been reading is anything to go by.
Steve
thanks going to give it a go now. there's look a bit to get my head round..when i done it ill upload.
---------- Post added at 06:36 PM ---------- Previous post was at 05:53 PM ----------
i have all the img files and im flashing them to the broken tablet now???do i need to package this up for people? or give me a list of which img files i need to upload
---------- Post added at 06:43 PM ---------- Previous post was at 06:36 PM ----------
rebooted and now i have a dead android on the screen, which im going to take as a good thing must be able to do some thing now
The main files needed are boot, kernel and recovery, if you can upload them then that would be a great help.
lonegunman said:
The main files needed are boot, kernel and recovery, if you can upload them then that would be a great help.
Click to expand...
Click to collapse
Thanks but they dont seem big enough they total up to 40mb were as the system.img is 589mb. also i cant give links on this site
but here it is in 7zip *=. with https:// in front
dl*dropboxusercontent*com/u/7167058/Output.7z
bigdaddy78 said:
Thanks but they dont seem big enough they total up to 40mb were as the system.img is 589mb. also i cant give links on this site
but here it is in 7zip *=. with https:// in front
dl*dropboxusercontent*com/u/7167058/Output.7z
Click to expand...
Click to collapse
Kernel is only 7 meg, both the boot and recovery have the kernel in them, so it's about right, will download and have a play in the morning as have a 4.30 start for work.
Help flashing
has anyone downloaded the files? I have tried to dump again to be on the safe side, but still no luck. i feel so close. im sure you will need the system.img aswell
Try this
flash this file to your tablet http://www.theattab.com/support-nine_dual.html , it will start but you will have no touchscreen, power the tablet off and then flash the boot,kernel and recovery img you made and see what happends.
its working!!!
Its working, i re flashed what i had and its booting into android. whats the best way for me to get it out to you all is there an easy way to package it up?? all i ask is that someone root the bloody thing. little bit worried as it seems to have my google account on it. isnt that stored in the userdata.img?
I flashed mine with the file that lonegunman suggested. Then flashed just the kernel.img to it as I was getting an error when I tried all 3 files. It seems to be working I will give it a proper check and post the end result. Of course if what I have done is likely to cause any problems then please let me know.
Looks like I spoke too soon. I don't seem to be able to enable the wireless at all. Stopped there as didn't seem much point in going further till that's sorted)
Steve
---------- Post added at 08:17 PM ---------- Previous post was at 08:05 PM ----------
bigdaddy78 said:
Its working, i re flashed what i had and its booting into android. whats the best way for me to get it out to you all is there an easy way to package it up?? all i ask is that someone root the bloody thing. little bit worried as it seems to have my google account on it. isnt that stored in the userdata.img?
Click to expand...
Click to collapse
If the previously bricked tablet is now working why not factory reset that one then dump image from it. No chance of personal data then.
Is your wireless working ok?
Steve
Indeed, the best thing to do is to flash all the parts, do a factory reset and dump again, there is a tool to make all the img files into 1 file, it's a little hard to explain it all but have a read here http://forum.xda-developers.com/showthread.php?t=2517181&page=2 , in a nutshell you will need to unpack the @tab image and replace all the .img files in the folders with your working .img and as a plus i think this software will root as well, if not then there is another bit that will, will sort out link later.
Can you upload the rest of the files minus the system img one please.
It looks like I finally have it working. Even the wifi
I had to grab a (broken) firmware for the 9dc (search Google for cnm firmware and look for the result that send you to zackehh's blog
Then unpack it using the tool suggested by lonegunman. Replace the boot, kernel and recovery.img files with the ones grabbed from bigdaddy78. Repack it and flash the resulting update_out.img to the tablet.
It looks like I will be able to sleep soundly tonight without worrying that the wife is gonna murder me in my sleep. (yes, it was HER tablet)
Thanks for all the assistance, you have both, quite literally, saved my life
If anyone wants the file I'm more than happy to upload it somewhere for you.
One thing that is a bit odd though is that the model number shows as VS TOUCHTAB 10.1DC
Oh well, at least it's working.
Yes thats because the firmware on the cnm site for the 9 dc is the for the 10.1 tablet, that's why we have all the problems, 1 thing to try is the 7 dc firmware and see if thats any better.
Sent from my GT-N7105 using Tapatalk 2
I tried the 7 dc one, works but the display is a bit big for my liking, any chance of the system.img from your working 9 being uploaded bigdaddy78?
cnm 9dc
can someone please re-upload the output.7z file? I have the same problem with this piece of junk tablet. thank you!
v3ng3ance said:
can someone please re-upload the output.7z file? I have the same problem with this piece of junk tablet. thank you!
Click to expand...
Click to collapse
I can do if you like but why not wait till we have a full working image.
Code:
PID: Null
IMEI: Null
Model :
DLL: LS990
BIN: LS990ZV4_04.51101.TOT
SWV:
SWOV:
Model Information Check Fail
000000000
Please help I've been troubleshooting for days, tried redownloaded huge TOT files, tried different cables different systems etc.
Does this mean I have a special version of the LS990 that can't be downgraded?
what does this mean?
Only similar issue I found is this: http://forum.xda-developers.com/showthread.php?t=2729056&page=2
The [email protected]$$ says "NM, I got it too work!!"
And doesn't share the solution :crying:
EDIT; I guess implicitly, the solution in is in the return the to stock guide for LG G2 Verizon mentioned in the earlier reply, but that won't help my Sprint LG G3. Different ballgame alltogether.
DOUBLE EDIT: Just re-read hyelton's Return to Stock thread for the 10th time in the G2 general section, nothing seems to jump out aside from the warning not to use 16GB files for 32GB phone. AFAIK, G3 only comes in 32GB so I don't think even that would apply.
Again, I'm left to wonder if I have some odd engineering sample or a tampered (previously rooted maybe) phone.
And yes, I've tried the generic LGUP_8974.dll from AutoPrime
Nobody encourtered this?
Is this really such a unique issue that no one has encountered this on the G3?
It has to be something simple right?
Why is the generic dll not working either, does anyone have an alternate dll I could try?
Can you maybe post some screen shots? This can help us to really help. Why are trying to to "Tot" back? Is it because of some sort of recovery problem or something? The reason I aak is because this maybe able to tell me/us how we can help you. Can you tell us what os(s) you have used? This maybe because the usb port(s) you are using maybe "dead" this could end up causing the phone to not be able to "talk" to the computer correctly.
screenshot
A screenshot would simple have the FAIL status on a red backround and the code from the OP:
Code:
PID: Null
IMEI: Null
Model :
DLL: LS990
BIN: LS990ZV4_04.51101.TOT
SWV:
SWOV:
Model Information Check Fail
000000000
This is on VirtualBox on a Macbook, USB ports are fine I'm able to copy to and from the phone, adb works, etc
Tried it on my Windows machine and get FailedPreviousLoad() BIN CRC (attached screen)
And my reason for downgrading is I'm on ZV6 and would like to root
Is the device bricked? This code cause many problems. You might end up having to go to sprint and getting a replacment device. I have never herd of this before. You may need to stop using any VM(s) it might have some sort of problem with your phone.
Yes but the tot not passing usually indicates a bad download
This is my downloaded file's md5 hash
ed593facd25e16597ebf3834f435b820
The problem is I have nothing to compare it to... the source at codefi.re doesn't have an MD5!
http://downloads.codefi.re/wolfgart/LG_G3/LS990/ZV4/LS990ZV4_04.51101.tot
As far as what happens in the VM that's a different problem and the one that I'm focused on since the TOT passes there, I get further
Could this phone have been tampered with? That's what it's starting to look like.... it's as if it thinks it's another device.
Do you have another DLL I could try? I'm at my wits end here
Have you looked in this thread http://forum.xda-developers.com/showthread.php?p=54912191 or asked for help there?
Edfunkycold
Have a great day!
Thanks, I'll scour it again
Thanks, but I have been reading that thread, it's where I got the TOT file link from in the first place, and yeah, I think I might post there too.
Just wanted my own thread for more exposure.
EDIT: There is a user on page 26 of that thread, but they are pretty much at the point of giving up.
It's starting to look like this mystery will go unsolved
TechShui said:
Thanks, but I have been reading that thread, it's where I got the TOT file link from in the first place, and yeah, I think I might post there too.
Just wanted my own thread for more exposure.
EDIT: There is a user on page 26 of that thread, but they are pretty much at the point of giving up.
It's starting to look like this mystery will go unsolved
Click to expand...
Click to collapse
Did you backup your EFS? It looks like it got cleared. I'm not sure how you can restore it now without TWRP..
Isn't EFS just for data? @engine95
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
Can you post a screenshot of the settings for the flash tool? I just want to see something
1619415 said:
Isn't EFS just for data? @engine95
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
Can you post a screenshot of the settings for the flash tool? I just want to see something
Click to expand...
Click to collapse
In the screenshots, everything is either null or zeros. That usually means the EFS got wiped. If it's not backed up it usually means a brick. And it'll be very lucky to save it.
I could be wrong. And I can't remember if Flashtool shows it that way? Or if he's cleared them for posting. But in the past, and if I'm seeing/remembering right. That's not a good sign.
I think in the International forum, autoprime might have posted a possible way to save it. Or it might have been in the irc.
EFS is what gives us all functionality of cell and data. Along with our personal Id to the phone. In a nutshell.
Edit: heres a post about EFS. http://forum.xda-developers.com/showthread.php?p=56058409&postcount=1 There's also a lot of links in the FAQ
that's a good guess, but I the IMEI is not missing from within About Phone, Model information
The phone boots and runs fine, just want it rooted. Tried PurpleDrake too and it said to downgrade
Tried stump, it says "Device has been patched"
I don't want to give up but I'm running out of ideas.
New root method posted in general seems to be working for a lot of people
I am having the exact same issue with "Model Information Check Fail" on an LG990
TechShui said:
that's a good guess, but I the IMEI is not missing from within About Phone, Model information
The phone boots and runs fine, just want it rooted. Tried PurpleDrake too and it said to downgrade
Tried stump, it says "Device has been patched"
I don't want to give up but I'm running out of ideas.
Click to expand...
Click to collapse
I get the same error message that my phone has been patched, which is why I have gone down this path. I also get model information failed, and I've tried tot's 4,6, and 8 and get the same result. Also, just like you I can reboot the phone and it works fine. So if you have found or happen to find something that will help this issue, please be sure and post what you did to fix it.
Thanks!!1
no situation? can u help me fix my phone? i flashed the wrong rom. no download screen. no recovery. pc recognizes the port though. LG FlashTool says this: PID: Null
IMEI: Null
Model :
DLL: LS990
BIN: LS990ZV4_04.51101.TOT
SWV:
SWOV:
Model Information Check Fail
000000000
i fix this error by flashing cloudi rom and selecting correct model bot you will need a custom recovery
UPDATED 3-30-2018:
Offical TWRP has been released for this device.
https://twrp.me/motorola/motorolamotox4.html
It seems to have a couple active maintainers.
TWRP builds linked from here are no longer active, but the bootable may remain important to use.
---
Update 05/31/2018:
Step 1: install or boot TWRP
Step 2: flash your desired root package (magisk, SuperSU, etc)
That's all.
Screenshot
mightysween said:
Screenshot
Click to expand...
Click to collapse
Now... on to building the device tree and vendor
UPDATE: Geez, this is VERY different than anything I have done before. There is no recovery image at all!? I need to get up to speed on these new filesystems, I guess.
Great news - thank you!
Any chance you could post a checksum for the modified boot.img? I'm just paranoid given our issues with corrupt downloads from the Moto server and Mega as of late!
caain said:
Great news - thank you!
Any chance you could post a checksum for the modified boot.img? I'm just paranoid given our issues with corrupt downloads from the Moto server and Mega as of late!
Click to expand...
Click to collapse
Done, check OP.
Also, have been trying to get it uploaded directly to XDA but not working... gives no errors, but maybe too big?
I did not realize I could not unlock the bootloader on the Amazon version of this phone.
I will probably have to return it and get a different phone.
Sucks.
EDIT: I specifically bought the device because it said unlocked. I didn't know it just meant carrier unlocked.
johnjingle said:
I did not realize I could not unlock the bootloader on the Amazon version of this phone.
I will probably have to return it and get a different phone.
Sucks.
Click to expand...
Click to collapse
Bummer... I suspect most of the variants other than the XT1900-1 may be in the same boat.
mightysween said:
Bummer... I suspect most of the variants other than the XT1900-1 may be in the same boat.
Click to expand...
Click to collapse
The phone is labeled on the box and the SKU in about phone as XT1900-1. Just can't get an unlock code from Motorola, I believe because I bought it through Amazon.
I'm willing to try anything to unlock. Don't want to have to return the phone, just won't deal with a locked bootloader.
It was a pain to get my old phone (Droid Turbo) unlocked and will not deal with the pain it was to do that again.
If anyone has advice PM me.
EDIT: Half the reason I buy stuff is to tinker with it as a hobby.
johnjingle said:
The phone is labeled on the box and the SKU in about phone as XT1900-1. Just can't get an unlock code from Motorola, I believe because I bought it through Amazon.
I'm willing to try anything to unlock. Don't want to have to return the phone, just won't deal with a locked bootloader.
It was a pain to get my old phone (Droid Turbo) unlocked and will not deal with the pain it was to do that again.
If anyone has advice PM me.
Click to expand...
Click to collapse
Ah, so restricted by IMEI. They did that with Moto Gs back a few years.
mightysween said:
Ah, so restricted by IMEI. They did that with Moto Gs back a few years.
Click to expand...
Click to collapse
So... If I return this phone and buy one from Best Buy do you think that bootloader would be unlockable?
I got one from best buy and yes i unlocked it
running on verizon. I just did this and waiting for the phone to finish booting up. Taking a while here.
---------- Post added at 03:22 AM ---------- Previous post was at 03:07 AM ----------
has anyone tried to flash recovery yet? Or is this way to much in infancy for that?
\
hotpl8 said:
I got one from best buy and yes i unlocked it
running on verizon. I just did this and waiting for the phone to finish booting up. Taking a while here.
---------- Post added at 03:22 AM ---------- Previous post was at 03:07 AM ----------
has anyone tried to flash recovery yet? Or is this way to much in infancy for that?
Click to expand...
Click to collapse
There is no recovery to flash Hopefully we can get device tree and vendor built... not going so hot on that front at the moment.
Something happened
I did as described above. And I got stuck on a boot loop left it for 15 min. or more I got back into fastboot and booted the boot.img again and it just kept reseting. I got into create an account and when I was done google play services wasnt working causing more issue. Is there a stock img that I can flash to get this back to stock>?
Is it the oem.img or am I into something worse here?
hotpl8 said:
I did as described above. And I got stuck on a boot loop left it for 15 min. or more I got back into fastboot and booted the boot.img again and it just kept reseting. I got into create an account and when I was done google play services wasnt working causing more issue. Is there a stock img that I can flash to get this back to stock>?
Is it the oem.img or am I into something worse here?
Click to expand...
Click to collapse
I'd wait for mightysween to weigh in on this. I haven't flashed his modified boot.img myself yet, though I did unlock the device in preparation for it. I forgot unlocking erases all userdata so I'm setting the thing up again.
We think what we downloaded from the Moto server in the other thread is a complete firmware package for the current X4 Fi build. It is untested apart from the boot.img, to my knowledge. Did you by chance look at your 'About Phone' screen before this? I would specifically be interested in what was under "Software Variant", "Software Channel", and "build number". You mentioned previously that you purchased your X4 from Best Buy, so we may be working with different animals as there are several X4 variants. I am no developer, but it's possible that the stock boot.img files differ between variants.
---------- Post added at 12:19 AM ---------- Previous post was at 12:11 AM ----------
mightysween said:
ONLY VERIFIED ON XT-1900-1 (payton_sprout/Project Fi) running NPW26.83-34-0-1 firmware
Click to expand...
Click to collapse
So my "Motorola version" under the "About Phone" heading does report NPW26.83-34-0-1. However, my build number reports NPW26.4. Is this what yours is reading? Software variant reads google_fi, software channel reads retus. I wonder if it wouldn't be a good idea to get a cross comparison on these figures from those with Amazon and Best Buy devices.
I've got cold feet on flashing the boot.img after hotpl8 ran into issues, but I'm wondering if it's due to the variant differences. The firmware we got from the Moto server is NPW26.83-34-0-1, baseband M660_7020.05.01.52.01R. It ought to work as a backup for Fi variants, but I'd hate to be the first one that flashes it. Just mailed my N6 back to Google yesterday, so I've got no backup.
For everybody worrying about the modified boot.img, I was able to flash it without issue and everything is running fine. Got Titanium BU and Root Explorer (and Busybox) running w/root privileges. Android Pay is borked, but unlocking the bootloader did that.
Bootloader Info:
AP fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-f02712d-171004
Baseband: M660_7020.05.01.052.01R PAYTON_NA_CUST
Product/Variant: payton XT1900-1 32GB P4
Serial Number: **********
CPU: SDM630 1.0 (2)
eMMC: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
DRAM: 3GB SAMSUNGLP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
Console[NULL]: null
Tools Mode Config: DISABLED
Power OK
oem_locked (before unlock)
flashing_unlocked (after unlock)
Software status: Official
Connect USB Data Cable (cable uncconected)
Transfer Mode: USB Connected (cable connected)
caain said:
I'd wait for mightysween to weigh in on this. I haven't flashed his modified boot.img myself yet, though I did unlock the device in preparation for it. I forgot unlocking erases all userdata so I'm setting the thing up again.
We think what we downloaded from the Moto server in the other thread is a complete firmware package for the current X4 Fi build. It is untested apart from the boot.img, to my knowledge. Did you by chance look at your 'About Phone' screen before this? I would specifically be interested in what was under "Software Variant", "Software Channel", and "build number". You mentioned previously that you purchased your X4 from Best Buy, so we may be working with different animals as there are several X4 variants. I am no developer, but it's possible that the stock boot.img files differ between variants.
---------- Post added at 12:19 AM ---------- Previous post was at 12:11 AM ----------
So my "Motorola version" under the "About Phone" heading does report NPW26.83-34-0-1. However, my build number reports NPW26.4. Is this what yours is reading? Software variant reads google_fi, software channel reads retus. I wonder if it wouldn't be a good idea to get a cross comparison on these figures from those with Amazon and Best Buy devices.
I've got cold feet on flashing the boot.img after hotpl8 ran into issues, but I'm wondering if it's due to the variant differences. The firmware we got from the Moto server is NPW26.83-34-0-1, baseband M660_7020.05.01.52.01R. It ought to work as a backup for Fi variants, but I'd hate to be the first one that flashes it. Just mailed my N6 back to Google yesterday, so I've got no backup.
Click to expand...
Click to collapse
build number: NPW26.4
MOTO Version: NPW26.83-34-0-1
Software channel: retus
Baseband Version: M660_7020.05.01.52.01 R PAYTON_NA_CUST
of course this is after I tried the method above. Not sure if this changed anything?
hotpl8 said:
build number: NPW26.4
MOTO Version: NPW26.83-34-0-1
Software channel: retus
Baseband Version: M660_7020.05.01.52.01 R PAYTON_NA_CUST
of course this is after I tried the method above. Not sure if this changed anything?
Click to expand...
Click to collapse
Probably not. But what does your "software variant" tag read?
Your moto version, baseband, and software channel are all identical to the Fi variant, it seems.
---------- Post added at 12:51 AM ---------- Previous post was at 12:48 AM ----------
DiDGR8 said:
For everybody worrying about the modified boot.img, I was able to flash it without issue and everything is running fine. Got Titanium BU and Root Explorer (and Busybox) running w/root privileges. Android Pay is borked, but unlocking the bootloader did that.
Click to expand...
Click to collapse
I gave it a whirl after setting up my phone again from the bootloader unlock. All went well after 2 or 3 reboots. My bootloader info looks the same as yours as well. I never used Android Pay anyway!
I posted on r/MotoX4 and r/Project Fi asking for "About Phone" info from the other variants. From hotpl8's comment it seems like the Best Buy variant is on the same build and baseband.
Has anyone seen anything in the firmware from the Moto server that suggests it is 100% Fi-specific? All I see is build and baseband references. I wonder if it could safely be used as a backup for all variants (assuming it is in fact intact).
caain said:
Probably not. But what does your "software variant" tag read?
Your moto version, baseband, and software channel are all identical to the Fi variant, it seems.
---------- Post added at 12:51 AM ---------- Previous post was at 12:48 AM ----------
I gave it a whirl after setting up my phone again from the bootloader unlock. All went well after 2 or 3 reboots. My bootloader info looks the same as yours as well. I never used Android Pay anyway!
I posted on r/MotoX4 and r/Project Fi asking for "About Phone" info from the other variants. From hotpl8's comment it seems like the Best Buy variant is on the same build and baseband.
Has anyone seen anything in the firmware from the Moto server that suggests it is 100% Fi-specific? All I see is build and baseband references. I wonder if it could safely be used as a backup for all variants (assuming it is in fact intact).
Click to expand...
Click to collapse
payton XT1900-1
Now I do not have much command on the SDK. My command prompt was letting me input and reboot but now I says its having an unknown error.
Where did you get the factory image for the Fi? Wonder if I can find the factory image for the non-fi variant
hotpl8 said:
I did as described above. And I got stuck on a boot loop left it for 15 min. or more I got back into fastboot and booted the boot.img again and it just kept reseting. I got into create an account and when I was done google play services wasnt working causing more issue. Is there a stock img that I can flash to get this back to stock>?
Is it the oem.img or am I into something worse here?
Click to expand...
Click to collapse
Just reading back through... I am not sure what the version from Best Buy is. This image was from the Project Fi version (which it says, in bold, at the top and bottom of the OP, where it also says not to flash it if you aren't familiar with the risks and getting yourself out of trouble)
If your firmware is the same as what is described in the OP, then just flash the stock boot.img from here:
https://drive.google.com/file/d/0ByZWXbOZqmVqbUV5T3ZvZEFBZ2M/view?usp=drivesdk
If not, then you will need to find yourself a factory image for whatever variant of the device you have.
hotpl8 said:
payton XT1900-1
Now I do not have much command on the SDK. My command prompt was letting me input and reboot but now I says its having an unknown error.
Where did you get the factory image for the Fi? Wonder if I can find the factory image for the non-fi variant
Click to expand...
Click to collapse
There is a 4+ page thread in this very forum about our struggles in trying to download the Project Fi variant factory image! I am not aware of any other factory images available at this time.
So I doubt there's too many others looking for this anymore (all I could find were a few old threads that seemed to fizzle out pretty quickly), but as some may remember, the existing pre-built CFAR for this phone that's widely available on the net didn't work for some reason. One person in the old threads here said that they eventually did get it to work after several failed initial attempts, but I didn't see any followup posts or explanations. Anyway, that particular version would flash successfully but would hang on the splash screen with a SEAndroid error and refuse to boot.
Thinking it might be a version mismatch or something, I tried generating a new CFAR based on the current firmware (ARA2, January 2018) using the default settings, but that only gave me a file that wouldn't even flash ("unsupported dev type"). So I dicked around with a few settings, generated another CFAR file, and voila - root for the USCC "Galaxy J3 6" on MM. The usual disclaimers apply of course, but I feel like you should be good with this one in case anyone still wants root on this thing.
Note: On the first flash, the phone booted only to the initial splash screen with the "Recovery Not SEAndroid Enforcing" error and a "Set Warranty Bit: Cache" one too. It'll hang here for a minute, but before long the phone will reboot. When it comes back those will be replaced by the usual yellow "Set Warranty Bit: Kernel" error. This time it'll boot to the Samsung logo and then reboot itself again. Third time is the charm, though - it should go ahead and boot fully now, and you're good to go.
Here's the file - http://www.mediafire.com/file/ugkdb...m-j320r4_j3lteusc_mmb29m.j320r4tys2ara2_t0.7z
Now, how bout a recovery? There's what claims to be an unofficial TWRP build for this phone ("j3lteusc") that exists online, but I could never get it working (flashes, but only boots to stock still). However, the official generic "j3lte" build (found here - https://dl.twrp.me/j3lte/) will flash and boot successfully, but for some reason touch doesn't work, making it kinda useless. Anyone know how to fix that?
(BTW, in case anyone's not aware, the 320R4 is already network unlocked and works fine on GSM, though the network mode and APN settings are only accessible through hidden menus until you enable Global Mode in the hidden LTE settings menu.)
I actually have a fully working TWRP for the SM-J320R4
with fully functional touch capabilities with f2fs support and otg support... if your interested let me know by private message or replying on here
---------- Post added at 08:47 PM ---------- Previous post was at 08:41 PM ----------
I also have a CFAR that works perfectly as well as some custom roms as well as xposed and multiple TWRP backups
J320r4 TWRP and ROMs, please? CFAR?
May I have access please? I have a j3lteusc/J320r4. It's my first root. Would love to find success! Also, will I need to flash the first release stock fw that was there before the OTA updates? Or is it fine to install and root on updated firmware it has now?
ZachariahLambert1 said:
I actually have a fully working TWRP for the SM-J320R4
with fully functional touch capabilities with f2fs support and otg support... if your interested let me know by private message or replying on here
---------- Post added at 08:47 PM ---------- Previous post was at 08:41 PM ----------
I also have a CFAR that works perfectly as well as some custom roms as well as xposed and multiple TWRP backups
Click to expand...
Click to collapse
lugnut2099 said:
(BTW, in case anyone's not aware, the 320R4 is already network unlocked and works fine on GSM, though the network mode and APN settings are only accessible through hidden menus until you enable Global Mode in the hidden LTE settings menu.)
Click to expand...
Click to collapse
Hi, help me please! How can I enable Global Mode, where is the hidden LTE settings menu?
This is a long-shot but essential if we're going to mess around with this phone with any degree of confidence or YOLO. Without this, there is no experimenting with global non-5G 7T Pro roms and partitions. The MSM for the OP7 Pro 5G for EE and Sprint never leaked, but that was a low-key phone. Let's do better with the T-Mobile McLaren.
Your mission is simple: Obtain the MSMDownloadTool and ops file (usually packaged together in a password-protected rar). You need that package and the password. These are device specific. Don't really care how the files are ultimately delivered as long as there's no encryption. Any info about the file or URL (e.g. https://s3.amazonaws.com/oneplussupport/...) is welcome.
I hate bounties or the thought of enforcing one, but expect donations if you succeed and avail yourself. Anonymity is also acceptable.
If you happen to find something we don't expect like global firmware for this phone, there's a separate bounty thread for that. I doubt it exists.
Relevant codenames and identifiers for our device:
HD1925
hotdogg
oneplus7tpronroxygen
HD61CB
I think @ddggttff3 asked them for this and they wouldn't send it to him for some reason. Maybe they misunderstood what he was asking for? A stock MSM image is just stock, so it doesn't make sense to not release it on XDA. It seems wasteful for a company to have to do extra remote recovery sessions when simply releasing a stock MSM image on XDA could save a company extra time and money.
I also asked OnePlus https://www.oneplus.com/support/contact for a MSM image for the OnePlus 7T Pro 5G McLaren, since it's critical for safe development. In my case, they did not say no, they just gave me a boilerplate response of, "About your concern we would like to inform you that we will take this as feedback and pass it along to our developer team so that this update can be rectified in the upcoming updates in the near future." They emailed me again asking for a further response and I haven't replied yet, because that second email was more obviously automated and did not have a name like the first one did. I think they could possibly let a tech post it to XDA, etc., if convinced by someone with experience like a XDA Recognized Developer.
jhofseth said:
I also asked OnePlus https://www.oneplus.com/support/contact for a MSM image for the OnePlus 7T Pro 5G McLaren, since it's critical for safe development. In my case, they did not say no, they just gave me a boilerplate response of, "About your concern we would like to inform you that we will take this as feedback and pass it along to our developer team so that this update can be rectified in the upcoming updates in the near future." They emailed me again asking for a further response and I haven't replied yet, because that second email was more obviously automated and did not have a name like the first one did. I think they could possibly let a tech post it to XDA, etc., if convinced by someone with experience like a XDA Recognized Developer.
Click to expand...
Click to collapse
I just got off a chat with an agent and they tell me I'll get a remote session with their technical team in 24-48 hours I'm gonna do my best to get the image/ password for you guys
tserv95 said:
I just got off a chat with an agent and they tell me I'll get a remote session with their technical team in 24-48 hours I'm gonna do my best to get the image/ password for you guys
Click to expand...
Click to collapse
Did it work out?
Still waiting from then
They never follow up. I'm still waiting a week later
LLStarks said:
They never follow up. I'm still waiting a week later
Click to expand...
Click to collapse
Same here, been about four days!
Unlucky. OnePlus is being pretty crappy with their service.
https://www.oneplus.com/support/contact has 3 contact options: phone (Call us +1 (833) 777-3633 7x24 hours), live chat and email. I really think a XDA Recognized Developer might have some luck getting a MSM image for the OnePlus 7T Pro 5G McLaren. There is a legitimate safe development need for this and providing it only benefits OnePlus and T-Mobile. The squeaky wheel gets the grease!
Barring actually getting the MSM I may have a method of recovery using fastboot and friends. However, I need the help of
a hotdogg owner with stock firmware & unlocked bootloader. The method is non-destructive (aside from the unlocking nuking
your data); just requires you to use fastboot to boot a twrp image and use adb to pull a partition (its 15gb, so to make it faster
you may want to use a real usb-c 3.0 cable; I don't think the orange one that comes with it is) and unpack it with a tool
called 'lpunpack' (unfortunately I don't know how to build it outside of an aosp/lineageos/grapheneos tree yet).
bad news, after waiting for days for a response from Oneplus, I decided to phone them. They state that after speaking to the remote support team, they cannot even help us. As they apparently don't have the images for the T-Mobile firmware either/ firmware for the Mclaren edition. This is a big bummer as until they (if they for that matter) release the firmware on support site we have no way of really recovering a bricked device and any firmware flashing is gonna be very dangerous to attempt. So yeah.. really regretting buying a T-Mobile variant Oneplus phone atm.
tserv95 said:
bad news, after waiting for days for a response from Oneplus, I decided to phone them. They state that after speaking to the remote support team, they cannot even help us. As they apparently don't have the images for the T-Mobile firmware either/ firmware for the Mclaren edition. This is a big bummer as until they (if they for that matter) release the firmware on support site we have no way of really recovering a bricked device and any firmware flashing is gonna be very dangerous to attempt. So yeah.. really regretting buying a T-Mobile variant Oneplus phone atm.
Click to expand...
Click to collapse
So, does T-Mobile flash the final firmware after OnePlus ships it to the US or something? If the firmware isn't finally flashed until it gets to the US, then that might make sense; but, if not, someone there could either be mistaken or less than truthful.
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
Maybe this will be a good avenue for us? https://twitter.com/tmobilehelp
tserv95 said:
bad news, after waiting for days for a response from Oneplus, I decided to phone them. They state that after speaking to the remote support team, they cannot even help us. As they apparently don't have the images for the T-Mobile firmware either/ firmware for the Mclaren edition. This is a big bummer as until they (if they for that matter) release the firmware on support site we have no way of really recovering a bricked device and any firmware flashing is gonna be very dangerous to attempt. So yeah.. really regretting buying a T-Mobile variant Oneplus phone atm.
Click to expand...
Click to collapse
Do you currently have one in an unflashed (to anything other than stock), unlocked state? If so I can probably guide you through how we can get a sort of
flashable stock image (flashed over fastboot). Hit me up if you are in that situation (sim unlocked, bootloader unlocked, and otherwise stock firmware).
---------- Post added at 11:50 AM ---------- Previous post was at 11:27 AM ----------
jhofseth said:
So, does T-Mobile flash the final firmware after OnePlus ships it to the US or something? If the firmware isn't finally flashed until it gets to the US, then that might make sense; but, if not, someone there could either be mistaken or less than truthful.
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
Maybe this will be a good avenue for us? https://twitter.com/tmobilehelp
Click to expand...
Click to collapse
Quite possible. I don't recall offhand but I believe mine came to me with version 10.0.14, and after 'recovering' from
flashing an experimental lineageos build on mine I ended up on version 10.0.13, which may be sort of the last common
ancestor for all the variants, and its now unable to OTA (it wants to go to 10.0.16, but as an incremental update it
can only jump versions 'in the correct order').
ntzrmtthihu777 said:
Barring actually getting the MSM I may have a method of recovery using fastboot and friends. However, I need the help of
a hotdogg owner with stock firmware & unlocked bootloader. The method is non-destructive (aside from the unlocking nuking
your data); just requires you to use fastboot to boot a twrp image and use adb to pull a partition (its 15gb, so to make it faster
you may want to use a real usb-c 3.0 cable; I don't think the orange one that comes with it is) and unpack it with a tool
called 'lpunpack' (unfortunately I don't know how to build it outside of an aosp/lineageos/grapheneos tree yet).
Click to expand...
Click to collapse
Getting my device tomorrow, but will obviously have to get it sim unlocked first, then wait the week for the OnePlus token to unlock the bootloader. But once I am at that point, I would happily do this if it could possibly lead to an alternate fastboot recovery method if no one is able to get the MSM tool. Obviously if anyone else can do this before I am able to, please do
ntzrmtthihu777 said:
Do you currently have one in an unflashed (to anything other than stock), unlocked state? If so I can probably guide you through how we can get a sort of
flashable stock image (flashed over fastboot). Hit me up if you are in that situation (sim unlocked, bootloader unlocked, and otherwise stock firmware).
Click to expand...
Click to collapse
I was wondering what particular device was mounted root, so I did: cat /proc/mounts
Apparently, / is /dev/block/dm-8
This is why TWRP is taking so long for Android 10: https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
"Android 10 also introduces a new dynamic partitioning system. Instead of having a dedicated system partition and a dedicated vendor partition, etc. Android 10 uses a super partition. I like to think of the super partition as a partition that contains a bunch of smaller partitions. One of the side effects of this dynamic partition system is that Google has chosen to use a form of the ext4 file system that is for all intents and purposes, read-only. This choice means that even if you wanted to, you can't easily mount and modify the system partition. We haven't really discussed this with other developers yet, but it may impact your ability to do things like install Gapps. In addition, the dynamic partition model means that eventually, we should probably provide you, the user, some GUI driven tools in TWRP to allow you to manage the dynamic partitions that are on the super partition." @Dees_Troy
jhofseth said:
I was wondering what particular device was mounted root, so I did: cat /proc/mounts
Apparently, / is /dev/block/dm-8
Click to expand...
Click to collapse
Yeah, but / is not terribly important compared to /system, /vendor, and /product (it is important tho)
jhofseth said:
This is why TWRP is taking so long for Android 10: https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Click to expand...
Click to collapse
Yeah, but twrp is not incredibly essential to the backup/restore process I've theorized about (still not sure about how it would work
in practice), just needed to get something to boot with root available without actually changing the stock firmware (by installing
magisk and such) in order to be able to pull the stock data.
---------- Post added at 12:38 PM ---------- Previous post was at 12:35 PM ----------
jhofseth said:
"Android 10 also introduces a new dynamic partitioning system. Instead of having a dedicated system partition and a dedicated vendor partition, etc. Android 10 uses a super partition. I like to think of the super partition as a partition that contains a bunch of smaller partitions. One of the side effects of this dynamic partition system is that Google has chosen to use a form of the ext4 file system that is for all intents and purposes, read-only. This choice means that even if you wanted to, you can't easily mount and modify the system partition. We haven't really discussed this with other developers yet, but it may impact your ability to do things like install Gapps. In addition, the dynamic partition model means that eventually, we should probably provide you, the user, some GUI driven tools in TWRP to allow you to manage the dynamic partitions that are on the super partition." @Dees_Troy
Click to expand...
Click to collapse
Yeah. This super partition is what I'm interested in. Once you copy it from the device (using adb pull /dev/block/.../super super.img)
you can extract it into its subpartitions using lpunpack. I believe one would be able to flash its subpartitions using fastboot in order
to recover from either a bad flash or a bad restore (like I and another user have, which left us on 10.0.13).
/dev/block/bootdevice/by-name/super
I made an image of super and file info reads 14.0 GiB (15,032,385,536).
That super.img compresses down to about 4.6 GiB in a regular zip file.
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
jhofseth said:
/dev/block/bootdevice/by-name/super
I made an image of super and file info reads 14.0 GiB (15,032,385,536).
That super.img compresses down to about 4.6 GiB in a regular zip file.
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Click to expand...
Click to collapse
Nice, nice. Yeah. that's to be expected. I think with that file I and dandroid would be able to restore our phones, assuming
that's stock firmware. Potentially others. Do you have a reliable means to share the file, if you're willing to? Per the link you
posted it contains no userdata so it should be safe to share.