Is there any way we can restore our phone using the files dumped by LGUP?
Right now I am considering perhaps flashing from fastboot every single file that was present but I am not sure if that could create an issue.
I believe it might also be possible to create a zip file using all the dump to create some kind of image that could be restore using TWRP?
i95swervin said:
You can use the partitions dumped from lg up to create a flashable twrp zip.
Click to expand...
Click to collapse
In order to do that, I can just put all the files into the zip (trimming the extra _COMYY at the end) and I can take the INF folder from another twrp zip?
Well actually I instead of all the files, maybe I should only overwrite the files with the same name since I believe the INF contain information about the other files.
Sorry if that sounds simple, most guides are for advanced people creating custom roms who knows what they are doing.
Duplicate Post
Does it sound like a good idea to flash all the partitions using flashboot?
flashboot flash aboot aboot_COMYY
flashboot flash abootbak abootbak_COMYY
flashboot flash apdp apdp_COMYY
etc...
Everything seems to indicate that it should works considering all the major components can be flashed that way.
Yes, you can flash with fastboot, however, you want to be VERY careful since there is no integrity check. So, you can end up flashing a corrupt boot chain if you have a noisy USB bus, and you phone is toast.
You should really consider making a flashable zip.
-- Brian
---------- Post added at 12:17 PM ---------- Previous post was at 12:17 PM ----------
Yes, you can flash with fastboot, however, you want to be VERY careful since there is no integrity check. So, you can end up flashing a corrupt boot chain if you have a noisy USB bus, and you phone is toast.
You should really consider making a flashable zip.
-- Brian
runningnak3d said:
Yes, you can flash with fastboot, however, you want to be VERY careful since there is no integrity check. So, you can end up flashing a corrupt boot chain if you have a noisy USB bus, and you phone is toast.
You should really consider making a flashable zip.
-- Brian
---------- Post added at 12:17 PM ---------- Previous post was at 12:17 PM ----------
Yes, you can flash with fastboot, however, you want to be VERY careful since there is no integrity check. So, you can end up flashing a corrupt boot chain if you have a noisy USB bus, and you phone is toast.
You should really consider making a flashable zip.
-- Brian
Click to expand...
Click to collapse
It did work for everything except the system partition. I believe this is because the phone only has 4GB of memory and the uncompressed file is over 5GB.
I ended up flashing the system partition using LGUP. I would have loved to say that everything is now fine for future members seeking to recover their device however I believe I messed up by using the system of the H915 (I thought I would try before flashing a H910 system since the H910 has much fewer options). The phone works (except signal) but I can't even flash anymore since the model of the phone appear as unknown within LGUP.... I can't edit the build.prop file either since it is protected. The troubles never ends.
Us the patched LG UP for cross flashing.
runningnak3d said:
Us the patched LG UP for cross flashing.
Click to expand...
Click to collapse
I did, it was working perfectly fine before. I could dump or flash, until I decided to only flash the system partition instead of all of them.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thinks my only options now are to find a way to get the phone recognized differently or to get the dll to bypass that check.
I have never gotten into a situation where the model was unknown, and I have had a version of laf from one model (H915), the engineering aboot which is identified as a US996, and yet a different system partition (VS995) all on an H910.
Not sure what you did if your are using the LG UP that was patched by smitel.
-- Brian
runningnak3d said:
I have never gotten into a situation where the model was unknown, and I have had a version of laf from one model (H915), the engineering aboot which is identified as a US996, and yet a different system partition (VS995) all on an H910.
Not sure what you did if your are using the LG UP that was patched by smitel.
-- Brian
Click to expand...
Click to collapse
Ok.... thats weird....
I tried a lots of stuff since then, mostly attempting to flash using LG Flash Tool using the following guide : https://forum.xda-developers.com/lg-g5/how-to/bring-lg-g5-to-life-download-mode-lgup-t3565508
Nothing worked, the kdz / dz kept failing even when they shouldn't.... My phone then wouldn't boot and kept displaying the (Factory Reset Status 2 / blue screen). At this point I thought it was bricked.... I couldn't do anything with the download mode and couldn't do anything with the phone either.
I thinks I tried one last time to upload the H910 build and it failed. I gave up and left the phone alone, still connected. Later, I came back and to my surprise the phone was booting up, better yet, it had signal which I never had with any rom / firmware, root or not.
Basically, I thinks my first attempt to restore entierly my phone except the system (I kept the H915) did work and solved all my problems. I am now able to use my phone with Telus (one of the canadian carrier) My original plan was to revert completely to the stock build I had and try to see if Rogers would give me signal since they apparently use the same bands as AT&T. But now that isn't necessary anymore.
Damn this is great, I can't even count the amount of time I got depressed by all that troubleshooting. Twice that I thought I had completely bricked my device. It is tougher than expected!
Really happy, plus the LG v20 is probably one of the best phone I have ever seen, it basically has all the features that are practically non-existent on the newer models.
Now I will just need to try to backup my current settings in one way or another, so that I never have to have any problems anymore. Especially if I plan on updating the device now that I receive updates.
Aknnor said:
I did, it was working perfectly fine before. I could dump or flash, until I decided to only flash the system partition instead of all of them.
Click to expand...
Click to collapse
It is sucessfully cross flashing system partition only? Thx U.
Can someone explain how to restore by backup using LGUP if I do not have TWRP access?
Right now my V20_H915 is stuck in a bootloop after a failed attempt to root. I have all my backup files by I don't know how to restore them onto the phone. I thought that when I do the backup it will just create a KDZ or BIN that I can flash with LGUP but that doesn't seem to be the case.
Hi all, I got an working AT&T G6 (H87110b). I want to try Convert/Upgrade the AT&T G6 to H873 OR US997 With VoLTE as guided in here. But there is a warning at the beginning as usual
Lets get those warnings out of the way! Warning Do this at your OWN RISK! There is NO WAY BACK to AT&T firmware at the moment and might never be. Only loss is you'll loose VoLTE and WiFi calling (If using the H873 Firmware)
Click to expand...
Click to collapse
I was thinking that trying this method to upgrade my G6 after making a full system backup using LG UP and make a KDZ file. If I can do that, I will able to come back in case if any bad thing happens after convert/upgrade.
Could anyone please guide me?
I .. i have Dump file from my LG device using lgup tool.... now how can i reflash these dump files again
naeembabakheil said:
I .. i have Dump file from my LG device using lgup tool.... now how can i reflash these dump files again
Click to expand...
Click to collapse
man, could you find the solution? I desperately need this now
master72 said:
man, could you find the solution? I desperately need this now
Click to expand...
Click to collapse
I was in the same boat. Since I just wanted some things, like contacts, and google authenticator DB I just used a tool that can read linux file system on windows. Those files are raw EFS4 partitions. Just using free 'Diskinternals Linux Reader'. You can rename the dumped partitions with an extension that the app wants, but I just hit '*' in the open box so it shows all files and opened them without renaming. Then saved the DBs out of it. They are readable with SQLite Browser.
But later i'm going to try what they said and use fastboot to flash a partition back to my phone. It was bricked good, but using LGUP on my H910 I was able to flash it with a canadian stock ROM and now it's an H915. Already ordered a new phone, mostly wanted my data, but to ease accessing it I will attempt to restore my data to it.
DaVinniCode said:
Yo estaba en el mismo barco. Como solo quería algunas cosas, como contactos y la base de datos del autenticador de Google, solo usé una herramienta que puede leer el sistema de archivos de Linux en Windows. Esos archivos son particiones EFS4 sin procesar. Simplemente usando el 'Diskinternals Linux Reader' gratuito. Puede cambiar el nombre de las particiones volcadas con una extensión que la aplicación quiera, pero solo presioné '*' en el cuadro abierto para que muestre todos los archivos y los abriera sin cambiar el nombre. Luego guardó los DB. Son legibles con SQLite Browser.
Pero luego intentaré lo que dijeron y usaré fastboot para actualizar una partición a mi teléfono. Estaba bien bloqueado, pero al usar LGUP en mi H910 pude flashearlo con una ROM de stock canadiense y ahora es un H915. Ya pedí un nuevo teléfono, en su mayoría quería mis datos, pero para facilitar el acceso intentaré restaurar mis datos en él.
Click to expand...
Click to collapse
No entiendo amigo, me puedes explicar mas detalladamente? Tengo un modem que volcado pero no se como instalarlo
Related
So i recently learned the L7 finally got the JB update. I decided to try it out, but i didn't like it overall.
So i have been trying to downgrade it, but no luck. I have been trying to use cmahendra's guide (http://forum.xda-developers.com/showthread.php?t=2085344), but this is meant for L9, and it keeps getting stuck on 4%, despite reinstalling drivers and following the trouble shooting on the guide.
Is there a way to downgrade to ICS, another guide maybe?
Thanks in advance
Jstag said:
So i recently learned the L7 finally got the JB update. I decided to try it out, but i didn't like it overall.
So i have been trying to downgrade it, but no luck. I have been trying to use cmahendra's guide (http://forum.xda-developers.com/showthread.php?t=2085344), but this is meant for L9, and it keeps getting stuck on 4%, despite reinstalling drivers and following the trouble shooting on the guide.
Is there a way to downgrade to ICS, another guide maybe?
Thanks in advance
Click to expand...
Click to collapse
I did it with the same guide and I had the same problem while downgrading (Lparam 1002 Error on 4%).
Check out my solution HERE
If you are afraid of doing changes at the MIDDLE of the operation, wait for it to get stuck, tell you to restart and before restarting it do the same changes i am proposing.
Cheers,
Moul
Solution
Jstag said:
So i recently learned the L7 finally got the JB update. I decided to try it out, but i didn't like it overall.
So i have been trying to downgrade it, but no luck. I have been trying to use cmahendra's guide (http://forum.xda-developers.com/showthread.php?t=2085344), but this is meant for L9, and it keeps getting stuck on 4%, despite reinstalling drivers and following the trouble shooting on the guide.
Is there a way to downgrade to ICS, another guide maybe?
Thanks in advance
Click to expand...
Click to collapse
Here is the solution !!!...
http://www.taringa.net/posts/celula...-Jelly-Bean-a-ICS-LG-L7-P700---705---708.html
pemon said:
Here is the solution !!!...
http://www.taringa.net/posts/celula...-Jelly-Bean-a-ICS-LG-L7-P700---705---708.html
Click to expand...
Click to collapse
That's what he has been doing .... LG mobile update tool is using KDZ-Updater.exe to do this job. You should check on Update tool's folder. There you'll find KDZ Updater I've been doing that also, correctly doing the same steps as EVERY guide online about KDZ updater, but still had the same issue.
It seems though that LG has some issues on downgrading firmwares, and I posted my solution to this problem.
P.S.(For JStag) Be sure you have :
1. Installed drivers correctly
2. Disable LG Modem driver in Device Manager
3. Have USB debugging on IF you are doing this with phone turned-on. If not, better if you put battery off and enter Emergency Download Mode before starting it.
Cheers,
Moul
OK
moulwxtos said:
That's what he has been doing .... LG mobile update tool is using KDZ-Updater.exe to do this job. You should check on Update tool's folder. There you'll find KDZ Updater I've been doing that also, correctly doing the same steps as EVERY guide online about KDZ updater, but still had the same issue.
It seems though that LG has some issues on downgrading firmwares, and I posted my solution to this problem.
P.S.(For JStag) Be sure you have :
1. Installed drivers correctly
2. Disable LG Modem driver in Device Manager
3. Have USB debugging on IF you are doing this with phone turned-on. If not, better if you put battery off and enter Emergency Download Mode before starting it.
Cheers,
Moul
Click to expand...
Click to collapse
Well, the important thing here is the special for the downgrade KDZ compiled by Homer ... As you mention if you are flashing a regular KDZ throws errors ...
===========
ESPAÑOL
===========
Pues aquí lo importante es el KDZ especial para el downgrade compilado por Homero... Como tu mencionas si flasheas con un KDZ normal arroja errores...
I bring this very good way to install a. KDZ (Rom stock) at LG G Pad, tested by me.
I do not take responsibility for the terminal to be kept as a brick, a billet, etc..
1: We downloaded the ROM for our team here: Firmware_LG_G_Pad
2: We got the LG mobile support tool and install it from here: http://csmg.lgmobile.com:9002/client/app/B2CAppSetup.exe
3: Download I install LG drivers if you have not already installed: Flash_Tool.1.0.54.rar - 3.35 MB
4: We lower the Install FlashTool (R&D Test Tool): Flash_Tool.1.0.54.rar - 3.35 MB
5: Unzip and run the UpTestEX.exe FlashTool.
6: In FlashTool window select:
- Select Type = 3GQCT.
{
"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"
}
- PhoneMode = DIAG.
- Select kdz file = Select the KDZ.
- Now Click "Normal web upgrade test".
- Now leave another window, you give it to "Start Upgrade".
- It will start to load the program.
- You wait a few seconds and another window will ask country and language.
- Country = Republic of Korea.
- Language = Inglés.
We left well, since we are Spanish, which is not to put the your country.
- To register the new language you press, Clear phone Software update Registry.
- And I will say that the record is complete.
- Press Ok.
- And start the flashing process.
7: I miss all this without connecting the tablet, the program tells me clearly that I normally do and connect without being in (ModoDowload) but to connect to the program detects it, has to be in LG software then clikais back into the program and you will recognize it, began to extract the KDZ and when you start Flash, one entered the tablet in ModoDowload after reboot everything perfect or bootloop or anything, all my settings such as tapeworms, but with the new version, but I recommend getting HardReset or factory reset.
8: How to do a hard reset after flashing (recommended)
1 - Shut off the tablet.
2 - with tight-volume button and the kindle Let the button pressed on with less volume.
Ye let go of the button again and, - 3 When the LG logo comes up, Put down the power button (leaving Tight-blasting time button), nothing more release, you apretáis the volume knob more and ignition time ignition and leaving the least volume and the tightest volume at once. Until the hard reset menu comes up.
4 - hard reset menu, apretáis the power button to confirm you 3 times. Restart in android and it will always do the wipes. Restarts one and you're set up everything again.
EYE, the terminal end and restart, but the pc does not open ended process, DO NOT DISCONNECT USB CABLE UNTIL END THE PROCESS IN THE PC.
Versions available for our Tablet
Video Demonstration
http://www.youtube.com/watch?v=EjxNUx_wfkc
Gracias por esta información. Le pregunto, cual es la diferencia entre los roms A, B y C?
Thanks for the info. One question though, what is the difference between rom version A, B and C?
JohnnySJ said:
Gracias por esta información. Le pregunto, cual es la diferencia entre los roms A, B y C?
Thanks for the info. One question though, what is the difference between rom version A, B and C?
Click to expand...
Click to collapse
According to the changelog OTA.
10a
10b improves AKP of LG.
10c improves the LCD.
YOUTUBE]EjxNUx_wfkc&[/YOUTUBE]
http://www.youtube.com/watch?v=EjxNUx_wfkc[/CENTER][/QUOTE]
it seems the link you posted to the video is broken but by reposting it worked(odd!!). a great thanks for the thread.
got a question:is the "c" firware with the lcd improvment downloadable and can i flash it over my "b" firmware and what is AKP and the lcd improvment?
:beer:
Sent from my Thrive using Tapatalk 2[/QUOTE]
Sent from my Thrive using Tapatalk 2
Marcosuper7 said:
5: Unzip and run the UpTestEX.exe FlashTool.
Click to expand...
Click to collapse
Actualy we have to run KDZ_FW_UDP.exe to be able to make it work, not "UpTestEX.exe"
Resolving
Anyone did?
Anyone here tried? it worked??
thanks
Hi,
I got a G Pad 8.3 that had some problems and did a bit of confusing things to it, like : I flashed a V510 base to it, which was causing several problems to the sound features.
Wanted to go back to stock and, with a little fear to brick it, decided to go fo this method, but mixed up with the one that you can find about the G2 elsewhere on the forum which provides the newest LG 2014 Flash tools.
So I downloaded the .kdz file for my device, and got some other settings in the Flash Tools (not in DIAG, but in Emergency - Did a CSE Flash which is a full wipe of everything - choose WCDMA instead of 3GQCT).
Well, I a happy to report that it worked and that I so was able to go back to a stock version in 4.2.2 mode instead of that stupidly unflashable 4.4.2 device.
I do believe that this worked well bacuase I was offered to upgrade via OTA (which of course, I did not !) and I know that usually this OTA upgrades are not offered to rooted or in any way modified devices.
BTW : I compiled CandyKAT for this device which works pretty nicely... so if you feel like, try it.
Regards.
All links for g pad 8.3 at this page don't work. I have 20d.
http://lg-phone-firmware.com/index.php?id_mod=39
Any ideas?
WKD622 said:
All links for g pad 8.3 at this page don't work. I have 20d.
http://lg-phone-firmware.com/index.php?id_mod=39
Any ideas?
Click to expand...
Click to collapse
I cannot find the STOCK 4.2.2 kdz for the v50020d Gpad.
I am in UK and have the same issue. Anyone had success with this?
Yeah, I Found an the solution First pick what you download and skip the ad.see the image
Change the "%2F" to "/" and Press Enter!! To Download It. Enjoy It!!!
Try this link for simpler click-and-download
http://www.lg-phones.org/official-stock-lg-g-pad-8-3-v500-rom-firmware.html
will this work from lollipop stock (korean) ?
edit: i tried this method from lollipop, it worked but after several tries and a brick (and a hard reset) i managed to put back kk
@Tazuya how did you get back to kk? i also flashed stock lp (hk). now i'm stuck on lp and it's really laggy. i've tried this method to get back to kk, won't work for me.
redhk886 said:
How did you get back to kk? i also flashed stock lp (hk). now i'm stuck on lp and it's really laggy. i've tried this method to get back to kk, won't work for me.
Click to expand...
Click to collapse
Get a 10A kdz. Flash with lg flashtool 2014 CSE/factory reset option and then update through lg official tool to latest KitKat!
where can i dl 10a? i've goggled but links are down. will this method acutally work? i've tried flashing 20a with lg flashtool, no success.
Try here http://lg-phone-firmware.com/index.php?id_mod=39 or http://devtester.ro/projects/lg-firmwares/ (use the country navigation).
links down : (
@redhk886: on both websites? I have the UK and the Romanian kdz. I uploaded V10B here https://mega.nz/#!nMtVwQbJ!Bj2SSB7-OlLBH4J0oRFf9WfU0M-sBf6IyurkMZ8CqIA (I believe it's the European version, I don't remember if it is UK or Romania). It is the oldest version I have.
it worked!!! thanks @Fullmetal Jun @tmihai20 . i thought it was bricked for a minute, kept looping lg logo, hard reset fixed it. now back to stock kk with root : ) thanks again guys.
Please help me. I am not familiar with any of this until now. I have learned a lot but also, I DO NOT WANT TO "BRICK" my device. I am unsure as to how it all works. Please read!!!! I want to be precise! More Information the better, right?
Problem:
I purchased a used Samsung Tab4 8GB SM-T230NU from a 3rd party. I got it home, connected it to the WiFi network, when I did that the browser + GooglePlay did not open, it would say "No Internet Connection" so I thought there might have been something that would not let it connect so I HARD RESET(once). Turn it back on, frozen at the Samsung Tab4 Logo Screen. If I press up it takes me to another screen "Team Win Recovery Project V2.8.0.1" I have tried EVERY OPTION from reset to recovery to restoring back to the last saved back-up. I have done what I can do without having to try "rooting" - "roms" - "firmware"(this is where I am a noob BUT WILLING TO LEARN)
My actions-
I called Samsung and they want me to send it in but they wanted to charge me money just to have it looked at. Next move I went to BestBuy, met with a Samsung Representative, he said he'd do it for me but I would have to leave my tablet overnight(he didn't have his own computer) I didn't think that would have been wise on my part so I had him write me instructions as to what I could do. He wrote: 1. Download ODIN(done) 2. Download SM-T230 Stock Rom. (downloaded+extracted files: StockRoms-Series_T230(NU)+V1.6.3)
This is as far as I have gotten, please get back to me. Thank you for taking the time in reading this.
Well, the solution is easier than you think, download this file
https://www.androidfilehost.com/?fid=24572369242687230
Put it in a micro sd you have, put that micro sd in the tablet and then reboot in recovery mode (power + home + up volume) then when you see that special menu go to where it says "wipe" then "advanced wipe" and select all The options minus external sd (which is your microsd where you have the zip, which I left) then, you give back and you give install (depending on your version of twrp can say up or down select storage) you choose that option and you go To sd, you choose the zip that I left and you give swipe to install, wait for it to install and then you reboot and ready, it would have to work, the tablet should be revived
in spanish/en español
bien, la solucion es mas facil de lo que crees, descarga este archivo
https://www.androidfilehost.com/?fid=24572369242687230
ponlo en alguna micro sd que tengas, pon esa micro sd en la tablet y despues, reiniciar en recovery mode (power+home+ subir volumen) entonces cuando veas ese menu especial ve a donde dice "wipe" despues "advanced wipe" y selecciona todas las opciones menos external sd (que es tu microsd donde tienes el zip, que te dejé) despues, le das a retroceder y le das a install (dependiendo de tu version de twrp puede decir arriba o abajo seleccionar almacenamiento) eliges esa opcion y vas a la sd, eliges el zip que te dejé y le das a swipe to install, esperas a que installe y despues le das a reboot y listo, tendria que funcionar, la tablet deberia de revivir
Here the post of the rom, it is not necessary that you read it as such, but anyway it is my obligation to leave it
https://forum.xda-developers.com/tab-4/development/rom-stock-t230-nu-acheron-rom-v1-0-2015-t3000107
I have 32gb SD card in my phone , I have 4gb of it used, and 28gb free. Would it matter if I have other files on SD card before inserting into tab4 with file?
Juzzzinlbs said:
I have 32gb SD card in my phone , I have 4gb of it used, and 28gb free. Would it matter if I have other files on SD card before inserting into tab4 with file?
Click to expand...
Click to collapse
No, it does not matter at all, as long as you have the zip on the SD, everything will work perfectly, LUCK
jimmy999x said:
Here the post of the rom, it is not necessary that you read it as such, but anyway it is my obligation to leave it
https://forum.xda-developers.com/tab-4/development/rom-stock-t230-nu-acheron-rom-v1-0-2015-t3000107
Click to expand...
Click to collapse
Is that because that is their program? What's your obligation?
I have managed to upload photos to an Album called Tab4. If you could teach me further, much appreciated.
(Deleted my post)
keikari said:
(Deleted my post)
Click to expand...
Click to collapse
Why would you do that?
Juzzzinlbs said:
Why would you do that?
Click to expand...
Click to collapse
I read your first post a bit carelessly, i just wrote about that you should use odin. And there are lot of tutorials how to use it. So my post was kind of unnecessary.
Would you agree with the method that jimmy just explained?
keikari said:
I read your first post a bit carelessly, i just wrote about that you should use odin. And there are lot of tutorials how to use it. So my post was kind of unnecessary.
Click to expand...
Click to collapse
Odin is not necessary, it would imply downloading many more files than you need, it already has twrp installed, so the only thing you need to revive the tablet is a custom rom
jimmy999x said:
Odin is not necessary, it would imply downloading many more files than you need, it already has twrp installed, so the only thing you need to revive the tablet is a custom rom
Click to expand...
Click to collapse
Not always, I once had wifi problem with samsung galxay ace and it didn't got fixed with changin rom, but after flashing stock firmware with odin it started to work. Of course TWRP flash is much faster, but with odin you can be almost 100% sure that it's a hardware issue if it doesn't work.
keikari said:
Not always, I once had wifi problem with samsung galxay ace and it didn't got fixed with changin rom, but after flashing stock firmware with odin it started to work. Of course TWRP flash is much faster, but with odin you can be almost 100% sure that it's a hardware issue if it doesn't work.
Click to expand...
Click to collapse
Sure, but that would be the plan b, for now just need to go the easy way, if it does not work, then we will proceed to use odin
jimmy999x said:
Sure, but that would be the plan b, for now just need to go the easy way, if it does not work, then we will proceed to use odin
Click to expand...
Click to collapse
If it doesn't work, is there a chance of bricking it?
Juzzzinlbs said:
If it doesn't work, is there a chance of bricking it?
Click to expand...
Click to collapse
Do not worry, if it does not work, the only thing that will not solve is the wi fi problem, the zip is functional to your device, the odin method will solve any problem, even wi fi, but it is that more time it takes, Try first with my method, if it does not work, we use odin
Okay so I did the steps you said, and it's not as easy as you put it.... Does anything like "SuperSU" mean anything?
Juzzzinlbs said:
Okay so I did the steps you said, and it's not as easy as you put it.... Does anything like "SuperSU" mean anything?
Click to expand...
Click to collapse
SuperSu is flashable .zip file which you flash in TWRP to get root access and root acceess is kind of similiar as being an administrator in windows(allows to do more stuff). I hope i understood your question correctly.
Yes. But when I go to do the wipe, it says wipe failed and in the terminal command screen it stops when it tries to update the partition details....
Juzzzinlbs said:
Yes. But when I go to do the wipe, it says wipe failed and in the terminal command screen it stops when it tries to update the partition details....
Click to expand...
Click to collapse
Thats weird. Well now you can try to install rom without wiping or do odin method.
keikari said:
Thats weird. Well now you can try to install rom without wiping or do odin method.
Click to expand...
Click to collapse
Could I possibly try adding the SuperSU root file?
Keep in mind it's still saying there is no OS installed
Hello guys, I'm desperated. Tried to install the .67 update and did it wrong. Now I have hard bricked my Moto G5 Plus.
I tried this, but no luck at all...
So, any help will be much appreciated.
LOG:
D:\Flia. Romano\Downloads\Android\Moto G5 Plus\blank-flash\blankflash>.\qboot.ex
e blank-flash
< waiting for device >
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 70 (0x46)
[ 0.004] ...cpu.sn = 2491206852 (0x947cccc4)
[ 0.004] Opening singleimage
[ 0.004] Loading package
[ 0.009] ...filename = singleimage.pkg.xml
[ 0.013] Loading programmer
[ 0.013] ...filename = programmer.mbn
[ 0.013] Sending programmer
[ 0.228] Handling things over to programmer
[ 0.228] Identifying CPU version
[ 0.230] Waiting for firehose to get ready
[ 11.341] ReadFile() failed, GetLastError()=0
[ 11.396] ReadFile() failed, GetLastError()=0
[ 11.399] ReadFile() failed, GetLastError()=0
[ 21.118] ReadFile() failed, GetLastError()=0
[ 21.173] ReadFile() failed, GetLastError()=0
[ 21.178] ReadFile() failed, GetLastError()=0
[ 60.508] Waiting for firehose to get ready
[ 63.509] WriteFile() failed, GetLastError()=0
[ 68.432] ReadFile() failed, GetLastError()=0
[ 97.252] ReadFile() failed, GetLastError()=0
[120.558] ...MSM8953 unknown
[120.558] Determining target secure state
[120.561] Waiting for firehose to get ready
[125.513] ReadFile() failed, GetLastError()=0
[181.382] ...secure = no
[181.405] Waiting for firehose to get ready
[241.438] Configuring device...
[241.441] Waiting for firehose to get ready
[301.479] Waiting for firehose to get ready
[361.512] Waiting for firehose to get ready
[421.657] Waiting for firehose to get ready
[482.043] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->devic
e_read()->IO error
[482.043] Check qboot_log.txt for more details
[482.043] Total time: 482.044s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffe
r_read()->device_read()->IO error
D:\Flia. Romano\Downloads\Android\Moto G5 Plus\blank-flash\blankflash>pause
Presione una tecla para continuar . . .
hola soy de argentina y tengo el mismo problema con un g5s plus como llo solucionaste?
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
MarckozZ said:
I MADE IT!!!!!! I HAVE MY POTTER BACK!!!!!!!!!!!!!
I'll be making a guide just in case anyone wants to try this... But it will be risky as hell!!! Tomorrow I'll make the guide + story of what I faced after flashing (IMEI = 0)!
Click to expand...
Click to collapse
hola tengo el mismo problema con un moto g5s plus como hiciste para solucionarlo
santiagoeg said:
hola soy de argentina y tengo el mismo problema con un g5s plus como llo solucionaste?
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
hola tengo el mismo problema con un moto g5s plus como hiciste para solucionarlo
Click to expand...
Click to collapse
Please follow XDA rules.
All threads should be in English only.
You can use Google translate to translate in English.
MarckozZ said:
Hello guys, I'm desperated. Tried to install the .67 update and did it wrong. Now I have hard bricked my Moto G5 Plus.
Now, this is my question. Can I unbrick it using the other methods there are to unbrick another Moto phones such as Moto G 2013 or Moto g4 Plus?
Or there are some specific files I must have to make it work?
I read I need some specific files... What should I do?
Click to expand...
Click to collapse
I bricked mine installing the 67 Ota update while rooted.. But wasn't hard bricked (please define hard bricked) as I could still boot to bootloader. I used windows pc program from here the moto g5 plus toolkit flashed stock
---------- Post added at 09:01 AM ---------- Previous post was at 08:59 AM ----------
alevity said:
I bricked mine installing the 67 Ota update while rooted.. But wasn't hard bricked (please define hard bricked) as I could still boot to bootloader. I used windows pc program from here the moto g5 plus toolkit flashed stock
Click to expand...
Click to collapse
I see your a senior member and don't mean to question you when you say hard bricked. Even if you can't get it to boot to bootloader the tool kit may still recognize it as connected
alevity said:
I bricked mine installing the 67 Ota update while rooted.. But wasn't hard bricked (please define hard bricked) as I could still boot to bootloader. I used windows pc program from here the moto g5 plus toolkit flashed stock
---------- Post added at 09:01 AM ---------- Previous post was at 08:59 AM ----------
I see your a senior member and don't mean to question you when you say hard bricked. Even if you can't get it to boot to bootloader the tool kit may still recognize it as connected
Click to expand...
Click to collapse
Well I had a Moto G, Moto G3 and this Moto G5 Plus, so I flashed things a LOT of times on the past two phones but, when I mean hard bricked here is HARD BRICKED!
No response at all, no bootloader screen or whatsoever, plus "qsusb_bulk" when plugging it to my PC: hard brick. I know that one member here made a blankfile to flash this device "potter" but it doesn't work for me... So, I'm pretty much trapped in this situation...
MarckozZ said:
Well I had a Moto G, Moto G3 and this Moto G5 Plus, so I flashed things a LOT of times on the past two phones but, when I mean hard bricked here is HARD BRICKED!
No response at all, no bootloader screen or whatsoever, plus "qsusb_bulk" when plugging it to my PC: hard brick. I know that one member here made a blankfile to flash this device "potter" but it doesn't work for me... So, I'm pretty much trapped in this situation...
Click to expand...
Click to collapse
Damn bro... Hmm.. I've been flashing since donut and I am soo grateful and probably just lucky I have never managed a hard brick.. Thought I did few times. Flashed wrong Rom as well once (luckily Samsung devices are lil easier to recover).. I have soft bricked and panic attacked myself so much over the years I seriously am starting to not want to do it anymore haha. I think we'll need to find a Motorola dev kit. Or possibly open it (not fun with this device video on youtube made me realize I won't be replacing the battery) and reset a jumper on the motherboard if that's even relevant with this device. It may have a soft fuse instead. But pretty much any hardware options are mute due to the low price of replacement....
---------- Post added at 09:23 AM ---------- Previous post was at 09:22 AM ----------
Not suggesting anything... But a hard bricked device is kinda hard to tell you rooted.. Oem unlock does supposedly register you with moto.. But how long ago did you buy and where.. And do you have a young teenage daughter who can go in crying
alevity said:
Damn bro... Hmm.. I've been flashing since donut and I am soo grateful and probably just lucky I have never managed a hard brick.. Thought I did few times. Flashed wrong Rom as well once (luckily Samsung devices are lil easier to recover).. I have soft bricked and panic attacked myself so much over the years I seriously am starting to not want to do it anymore haha. I think we'll need to find a Motorola dev kit. Or possibly open it (not fun with this device video on youtube made me realize I won't be replacing the battery) and reset a jumper on the motherboard if that's even relevant with this device. It may have a soft fuse instead. But pretty much any hardware options are mute due to the low price of replacement....
---------- Post added at 09:23 AM ---------- Previous post was at 09:22 AM ----------
Not suggesting anything... But a hard bricked device is kinda hard to tell you rooted.. Oem unlock does supposedly register you with moto.. But how long ago did you buy and where.. And do you have a young teenage daughter who can go in crying
Click to expand...
Click to collapse
LOL, This device has less than one month old, I unlocked the bootloader today and instantly flashed the LATAM firmware and tried the .67 OTA and it died, And no kids! So, I'm screwed! Great isn't it?
I'll have to save to buy another phone until some solution comes up ( @vache please help!!!)
MarckozZ said:
LOL, This device has less than one month old, I unlocked the bootloader today and instantly flashed the LATAM firmware and tried the .67 OTA and it died, And no kids! So, I'm screwed! Great isn't it?
I'll have to save to buy another phone until some solution comes up ( @vache please help!!!)
Click to expand...
Click to collapse
Did you try with the linux recovery tools?
Probaste con el script en linux?
Cronoss said:
Did you try with the linux recovery tools?
Probaste con el script en linux?
Click to expand...
Click to collapse
No tengo una PC con dual boot y Linux por ahora... Vere si lo puedo mandar a un service.
I don't have a PC with dual boot and Linux at the moment... I'll see if I can send it to a service center.
MarckozZ said:
No tengo una PC con dual boot y Linux por ahora... Vere si lo puedo mandar a un service.
I don't have a PC with dual boot and Linux at the moment... I'll see if I can send it to a service center.
Click to expand...
Click to collapse
Proba con virtualbox que es gratis. Bajate Ubuntu y hacelo desde ahi. No es dificil. Vale la pena probar.
Try installing virtualbox which is free. Download something like Ubuntu and do it from there. It's not hard.
Cronoss said:
Proba con virtualbox que es gratis. Bajate Ubuntu y hacelo desde ahi. No es dificil. Vale la pena probar.
Try installing virtualbox which is free. Download something like Ubuntu and do it from there. It's not hard.
Click to expand...
Click to collapse
I'll try this. The thing is I don't have enough RAM to run a VirtualBox instance, So I'll have to make another partition
Same thing happened to me and I'm visiting another country. What a nightmare.
Tomadock said:
Same thing happened to me and I'm visiting another country. What a nightmare.
Click to expand...
Click to collapse
Yea bro... I'll try to find a way to get this solved!
Cheering for you all
Its been a long while, but I'm pretty sure if it says qusb_bulk when you plug it into USB, then all hope isn't lost. A quick google of "qusb_bulk fix" brings up a lot of results and things to try. Maybe start here. https://www.google.com/amp/s/amp.reddit.com/r/MotoX/comments/4dt59q/qhsusb_bulk_fix/
itslels said:
Its been a long while, but I'm pretty sure if it says qusb_bulk when you plug it into USB, then all hope isn't lost. A quick google of "qusb_bulk fix" brings up a lot of results and things to try. Maybe start here. https://www.google.com/amp/s/amp.reddit.com/r/MotoX/comments/4dt59q/qhsusb_bulk_fix/
Click to expand...
Click to collapse
Thanks for coming bro. Already tried this and it doesn't work! 'll have to live with this until devs come up with new blankflash files to revive this thing!
@MarckozZ
Sorry for the bad english, I'm at fault in this but the google translator too.
Hello Friend, I went through the same situation as you with the .67 update. Although I unlocked the bootloader and invalidated the warranty, I decided to take it to the assistance of the motorola, because I believe that its technicians are trained and because it is a local representative of the motorola, they are also honest ... just to hear from them that I needed to change the Plate and the cost for this is half a new here in Brazil. But after much research, I was convinced that it was not the card, so I opened the device and gave a shock to the battery, do not ask me why I did this, probably the desperation made me do it, but it did not help, the device continued unplugged , It just blinked the led when it was connected and was identified by the PC device manager, so I gave up for a while.
But as I was not happy using my motoE1 I decided to try one more time, it was when I came across this post:
Https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
And tried using the blankflash made available by vache for the potter but did not succeed in any of the countless attempts.
So I concluded that the .67 update should have been upgraded and so it was not possible to go back with the blankflash, but browsing through the tree of vache folders I saw that it had also available for the albus (MotoZ2Play) and I decided to take a risk, and because there A certain similarity between the two devices and this latest one worked out. I know I will be criticized for recommending this to you, but it was the only solution I got, but I can not fail to mention that after doing that things will not be the same anymore.
After having success with the tutorial of the above link using the blankflash of MotoZ2play that you can find here
Http://cloud.vache-android.com/Moto/albus/blankflash/
You have to use bootloader, gpt and addison recovery (MotoZplay)
Https://drive.google.com/open?id=0B7X6bQHmiX_BY29Damx5ejEyX1U
To return to stock rom.
It's important to do this right after the blankflash tutorial here:
Https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
Once this is done you can use the Moto.G5.Toolkit available here
Https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
To install NPN25.137-33 / 35, but do not forget to replace bootloader, gpt and recovery in the firmware folder.
Remember, that was the decision I made, so do it at your own risk, although the risk here is to bring it back, I do not know what it will be with future updates.
Good luck!
Paulo Narley said:
@MarckozZ
Sorry for the bad english, I'm at fault in this but the google translator too.
Hello Friend, I went through the same situation as you with the .67 update. Although I unlocked the bootloader and invalidated the warranty, I decided to take it to the assistance of the motorola, because I believe that its technicians are trained and because it is a local representative of the motorola, they are also honest ... just to hear from them that I needed to change the Plate and the cost for this is half a new here in Brazil. But after much research, I was convinced that it was not the card, so I opened the device and gave a shock to the battery, do not ask me why I did this, probably the desperation made me do it, but it did not help, the device continued unplugged , It just blinked the led when it was connected and was identified by the PC device manager, so I gave up for a while.
But as I was not happy using my motoE1 I decided to try one more time, it was when I came across this post:
Https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
And tried using the blankflash made available by vache for the potter but did not succeed in any of the countless attempts.
So I concluded that the .67 update should have been upgraded and so it was not possible to go back with the blankflash, but browsing through the tree of vache folders I saw that it had also available for the albus (MotoZ2Play) and I decided to take a risk, and because there A certain similarity between the two devices and this latest one worked out. I know I will be criticized for recommending this to you, but it was the only solution I got, but I can not fail to mention that after doing that things will not be the same anymore.
After having success with the tutorial of the above link using the blankflash of MotoZ2play that you can find here
Http://cloud.vache-android.com/Moto/albus/blankflash/
You have to use bootloader, gpt and addison recovery (MotoZplay)
Https://drive.google.com/open?id=0B7X6bQHmiX_BY29Damx5ejEyX1U
To return to stock rom.
It's important to do this right after the blankflash tutorial here:
Https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
Once this is done you can use the Moto.G5.Toolkit available here
Https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
To install NPN25.137-33 / 35, but do not forget to replace bootloader, gpt and recovery in the firmware folder.
Remember, that was the decision I made, so do it at your own risk, although the risk here is to bring it back, I do not know what it will be with future updates.
Good luck!
Click to expand...
Click to collapse
IT WORKED!!!!
Well at least partially... I can enter bootloader now but, when I flash the firmware (using gpt, bootloader and recovery you gave) it only starts and shows the unlocked bootloader warning and restarts... So, it turns on now but I cant pass that warning screen.
Any suggestions?
What I did was this:
*blankflashed the albus files
*flashed the entire firmware (from US, 135-35)
Restarted but got a bootloop.. then..
*reflashed firmware but replacing bootloader, gpt and recovery from Z play (forgot to do this the first time )..
and still have a bootloop on the warning screen... am I missing something? Did you phone instantly rebooted as usual?
SO, basically what I will have is a Moto G5 Plus with Moto Z Play bootloader, GPT and recovery..
MarckozZ said:
IT WORKED!!!!
Well at least partially... I can enter bootloader now but, when I flash the firmware (using gpt, bootloader and recovery you gave) it only starts and shows the unlocked bootloader warning and restarts... So, it turns on now but I cant pass that warning screen.
Any suggestions?
What I did was this:
*blankflashed the albus files
*flashed the entire firmware (from US, 135-35)
Restarted but got a bootloop.. then..
*reflashed firmware but replacing bootloader, gpt and recovery from Z play (forgot to do this the first time )..
and still have a bootloop on the warning screen... am I missing something? Did you phone instantly rebooted as usual?
SO, basically what I will have is a Moto G5 Plus with Moto Z Play bootloader, GPT and recovery..
Click to expand...
Click to collapse
Super exciting that it's at least getting a boot loaded now.. I wondered if by any chance the issue now is that your trying to flash a stock rom that is a downgrade from the updated 67.. If it even recognized the update before bricking
alevity said:
Super exciting that it's at least getting a boot loaded now.. I wondered if by any chance the issue now is that your trying to flash a stock rom that is a downgrade from the updated 67.. If it even recognized the update before bricking
Click to expand...
Click to collapse
I sideloaded the OTA via adb, and the recovery flashed it without any problems at that moment... So it had the .67 update installed but also a corrupted bootloader.
Now, it doesn't have the .67 update anymore since i flashed the 135.35 US firmware. So the system has the 135.35 version, but with the recovery, partition table and bootloader from Moto Z Play.
After I push the power button it shows the warrning screen and either stays there, bootloops or shows a recovery screen with the circle animation with the word "Erasing" beneath, and then bootloop again.
My guess is that bootloader searchs for a suitable Moto Z Play firmware and, since it has another, it won't boot at all.
Also I'm worried now. Since this phone now has software parts fron another Moto phone, I wonder if I will be able to flash gpt.bin and bootloader.img from the upcoming O firmware. I'll die if now I'm only able to flash things from Moto Z Play instead of potter..
:fingers-crossed:
MarckozZ said:
I sideloaded the OTA via adb, and the recovery flashed it without any problems at that moment... So it had the .67 update installed but also a corrupted bootloader.
Now, it doesn't have the .67 update anymore since i flashed the 135.35 US firmware. So the system has the 135.35 version, but with the recovery, partition table and bootloader from Moto Z Play.
After I push the power button it shows the warrning screen and either stays there, bootloops or shows a recovery screen with the circle animation with the word "Erasing" beneath, and then bootloop again.
My guess is that bootloader searchs for a suitable Moto Z Play firmware and, since it has another, it won't boot at all.
Also I'm worried now. Since this phone now has software parts fron another Moto phone, I wonder if I will be able to flash gpt.bin and bootloader.img from the upcoming O firmware. I'll die if now I'm only able to flash things from Moto Z Play instead of potter..
Click to expand...
Click to collapse
After the albus blankflash you need to install the bootloader and gpt and reboot to the bootloader, then replace in the firmware folder NPN25.137-33 or 35 the bootloader gpt and recovery and then install all the firmware stock using the method you I recommend using Moto.G5.Toolkit to make everything easier, I have re-done the process of installing update .67 only to confirm that I would have the same problem and these steps helped me to solve it again.
This is obvious at this point, but pressing volume down + power does nothing? just shows the warning screen and loops?
so i bought this Tab E (SM-T377V) off a site , and it was owned by a resturant that no longer used the service Doordash. it was locked down with FRP lock when i first got it i was able to by pass the FRP and i can flash any ROM to it now but it always loads the KNOX customization no matter what ROM i try and load .. now in 5.1.1 i can get root but when i try and remove the KNOX it freezes and wont boot. right now i can let knox load and use it normally for the most part just has the doordash logo wallpaper which is set with the KNOX. i would like to try and get rid of this KNOX customization , i assume there is a hidden partition or something like that makes it point too the KNOX loading no matter what i flash it with? in ODIN i've tried to do the erase nand and everything else i can but still no luck any help or advise would be useful, on another note i have the COMBONATION FILE ROM and when i load that i don't get the KNOX thing but its just alot of testing stuff is there anyway i can use that to remove this KNOX??? again any advise or pointers would be helpful. right now like i said i got it usable as a tablet just with annoying with the doordash customizations ..
Any luck?
cernorama said:
so i bought this Tab E (SM-T377V) off a site , and it was owned by a resturant that no longer used the service Doordash. it was locked down with FRP lock when i first got it i was able to by pass the FRP and i can flash any ROM to it now but it always loads the KNOX customization no matter what ROM i try and load .. now in 5.1.1 i can get root but when i try and remove the KNOX it freezes and wont boot. right now i can let knox load and use it normally for the most part just has the doordash logo wallpaper which is set with the KNOX. i would like to try and get rid of this KNOX customization , i assume there is a hidden partition or something like that makes it point too the KNOX loading no matter what i flash it with? in ODIN i've tried to do the erase nand and everything else i can but still no luck any help or advise would be useful, on another note i have the COMBONATION FILE ROM and when i load that i don't get the KNOX thing but its just alot of testing stuff is there anyway i can use that to remove this KNOX??? again any advise or pointers would be helpful. right now like i said i got it usable as a tablet just with annoying with the doordash customizations ..
Click to expand...
Click to collapse
Just factory reset with twrp and format the data partition.
Ensure oem unlock is enabled first.
cernorama said:
so i bought this Tab E (SM-T377V) off a site , and it was owned by a resturant that no longer used the service Doordash. it was locked down with FRP lock when i first got it i was able to by pass the FRP and i can flash any ROM to it now but it always loads the KNOX customization no matter what ROM i try and load .. now in 5.1.1 i can get root but when i try and remove the KNOX it freezes and wont boot. right now i can let knox load and use it normally for the most part just has the doordash logo wallpaper which is set with the KNOX. i would like to try and get rid of this KNOX customization , i assume there is a hidden partition or something like that makes it point too the KNOX loading no matter what i flash it with? in ODIN i've tried to do the erase nand and everything else i can but still no luck any help or advise would be useful, on another note i have the COMBONATION FILE ROM and when i load that i don't get the KNOX thing but its just alot of testing stuff is there anyway i can use that to remove this KNOX??? again any advise or pointers would be helpful. right now like i said i got it usable as a tablet just with annoying with the doordash customizations ..
Click to expand...
Click to collapse
Hola gracias a Google Translate eh podido entender tu pregunta.
Veras, yo tengo el mismo problema,.
Ya casi tengo lista la tablet, pero aun no puedo activar la WiFi del dispositivo.
Yo usé la Samsung tools + Hack file.
Ya puedo usar la tablet pero no me permite navegar por internet porque el WiFi esta bloqueado
Si tienes alguna idea me la comparte y yo te doy lo que tengo de investigacion.
Saludos
IDK if you figured this one out but here is how I did it:
>Extract PIT file from the BL tar.md5 of your stock firmware
>Nand erase all with Odin 3.07 with autoreboot UNCHECKED
>Set PIT file and check repartition, reboot download mode
>Flash stock firmware
If anyone needs links PM me. I have a Sammobile account.
hi just flash this combination and activ usb debug and oem unlock make hard reset
COMBINATION_VZW_FA51_T377VVRU1AQD1_VZWFAC_CL6507601_QB13278124_REV00_user_mid_noship
flash this rom ALL_VZW_T377VVRU1AOL7_T377VVZW1AOL7_5.1.1_USA
thats all
Lol just go to safe mode and then put the wrong password in 30 times
help!
Having trouble doing this. Would you be able to help me with the process? Got a practically new tablet preloaded with Doordash. Thank-you!
2 more tablets , reset and cleared
i got 2 more doordash tablets SM-T377v , i was able to odin flash the combonation file .. unlock oem and usb debugger in developers options, and then flash the latest 7.1 rom , both work like a charm now , from what i have read the OEM unlock disables the KNOX .
Where can I find this combination file?
HI, im having a very similar issue with my device i just got. Its a tab e (SM-T567V) i tried flashing a new rom and every time it connects to wifi Knox pops up and locks it out. What rom and steps should i be using to fix this? I have the ability to oem unlock and USB debug it. Thanks any info would be greatly appreciated
I have same tablet and same issue. How did you get it reset? Where can I find that combination file?
MarXilla said:
IDK if you figured this one out but here is how I did it:
>Extract PIT file from the BL tar.md5 of your stock firmware
>Nand erase all with Odin 3.07 with autoreboot UNCHECKED
>Set PIT file and check repartition, reboot download mode
>Flash stock firmware
If anyone needs links PM me. I have a Sammobile account.
Click to expand...
Click to collapse
Hey can I please get those links? I'm ready to conquer this damn thing... Lol
cernorama said:
2 more tablets , reset and cleared
i got 2 more doordash tablets SM-T377v , i was able to odin flash the combonation file .. unlock oem and usb debugger in developers options, and then flash the latest 7.1 rom , both work like a charm now , from what i have read the OEM unlock disables the KNOX .
Click to expand...
Click to collapse
Can you please tell me where that combination file is? And also how to own unlock...it's not in the settings
I am also having same issue with t387V, I was able to flash combination file and oem unlock; however when I flash the stock firmware with ODIN, the MDM (mobicontrol) is still present.
For above, you can try to find combination file here https://firmwarex.net/?s=t377v
neozengar said:
I am also having same issue with t387V, I was able to flash combination file and oem unlock; however when I flash the stock firmware with ODIN, the MDM (mobicontrol) is still present.
For above, you can try to find combination file here https://firmwarex.net/?s=t377v
Click to expand...
Click to collapse
I have the Samsung SM-T387v as well. Did you ever figure a fix for this?
8wrlobo said:
Lol just go to safe mode and then put the wrong password in 30 times
Click to expand...
Click to collapse
Unfortunately, that didn't work
MarXilla said:
IDK if you figured this one out but here is how I did it:
>Extract PIT file from the BL tar.md5 of your stock firmware
>Nand erase all with Odin 3.07 with autoreboot UNCHECKED
>Set PIT file and check repartition, reboot download mode
>Flash stock firmware
If anyone needs links PM me. I have a Sammobile account.
Click to expand...
Click to collapse
Hi, I'm having the same issue. Samsung Galaxy Tab A, SM-T387v.
I have no idea how to do what you just said. Can you or someone please explain so that I may perform the necessary actions to fix my tablet?
I have the T-378V also. You can get access to developer mode by interrupting Soti Mobicontrol during initial setup. You can do this by restarting in safe mode as soon as device setup has started following setting up your work device. Now, there are comments regarding several methods of proceeding: 1)Try to Nand erase all, flash pit from combo file ? and then flash stock fw? 2) Wait out the 7 days with sim inserted, wifi on and, in safe mode to unlock oem? What step proceeds at that point abd twrp? 3)There is a method involved of encrypting the device and incorrectly entering the password to factory reset, however without having encryption and oem unlock enabled this option hasn’t worked for me. 4) One of the fw I flashed with odin made an unlock symbol show up at the bottom of the android/samsung boot up logo I don’t know what the significance was or how to proceed.
If anyone figures something out please share it here.
MarXilla said:
IDK if you figured this one out but here is how I did it:
>Extract PIT file from the BL tar.md5 of your stock firmware
>Nand erase all with Odin 3.07 with autoreboot UNCHECKED
>Set PIT file and check repartition, reboot download mode
>Flash stock firmware
If anyone needs links PM me. I have a Sammobile account.
Click to expand...
Click to collapse
It didn't work for me.