[CLOSED] Delete - Samsung Galaxy A70 Guides, News, & Discussion

Mod edit: Thread closed as the threadowner removed the content of the opening post! Oswald Boelcke, Senior Moderator
Delete

Thanks @MarvinMod. Followed all the instructions to the letter and rooted my device with no problems.

Hello, I cannot get this to work.
I am stuck on this step:
***************************
4- On your PC open odin, click options and uncheck auto reboot, click Log, click AP, select the recovery.zip file, click start. Wait for Pass
***************************
Odin tries to upload the recovery.tar file (.tar, not .zip) but at the end it fails. Then I have to reboot the phone and wait, patiently, until it boots into Android, then, and only then can I try to switch it off, and all over again.
This is from Odin
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 78 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> vbmeta.img
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Zilliman said:
Hello, I cannot get this to work.
I am stuck on this step:
***************************
4- On your PC open odin, click options and uncheck auto reboot, click Log, click AP, select the recovery.zip file, click start. Wait for Pass
***************************
Odin tries to upload the recovery.tar file (.tar, not .zip) but at the end it fails. Then I have to reboot the phone and wait, patiently, until it boots into Android, then, and only then can I try to switch it off, and all over again.
This is from Odin
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 78 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> vbmeta.img
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Did you make sure oem unlock is checked in development options before booting to download mode and flashing recovery.tar with odin? (Step 2). You must boot to Android, check oem unlock then boot to download mode and flash. Is the bootloader unlocked? Check to make sure your using odin version i supplied under the tools link bottom of guide. Im not at my PC but the version that I know works is 3.13.3 or something close to that, ill confirm later when home.

Could you please help me by looking there - I think the phone is bricked...
Have I just bricked my faithful A70?
So I tried to install TWRP and followed the steps, used ODIN v3.14, it tried to upload something but failed with an error. Now the phone has gone into a perpetual restart cycle: 1) Reboot (by itself or Vol Down + Power) 2) Blank screen with...
forum.xda-developers.com

Zilliman said:
Could you please help me by looking there - I think the phone is bricked...
Have I just bricked my faithful A70?
So I tried to install TWRP and followed the steps, used ODIN v3.14, it tried to upload something but failed with an error. Now the phone has gone into a perpetual restart cycle: 1) Reboot (by itself or Vol Down + Power) 2) Blank screen with...
forum.xda-developers.com
Click to expand...
Click to collapse
You can't hard brick the A70 and sure thing. I posted a comment on your post you made. If its in a bootloop, hold vol up and down during the bootloop while connected to a PC till it boots to download mode. Then flash latest stock and reboot.
Also, you need odin version 3.13.3, youll find it in the tools link at bottom of guide.

Can't wait to do this.
Question though, what is the "Pass Safetynet"?

Damn.... does this mean i can not do this?

SuperDroid519 said:
Damn.... does this mean i can not do this?
Click to expand...
Click to collapse
As far as i know, the a705w in not unlockable but i dont have one so i cant do tests. Here is a thred that you could try but im not bent if you dont.
Root Samsung Galaxy A70 SM-A705W With Odin Tool - Root Droids
This Guide line provides instructions to root Samsung Galaxy A70 SM-A705W phone with Pictures. And we give you CF Root file, Oding program and Samsung Galaxy drivers as well you can find lot of solutions for rooting errors. From this CF root file, you can only root Samsung Galaxy A70 SM-A705W –...
www.rootdroids.com

SuperDroid519 said:
Can't wait to do this.
Question though, what is the "Pass Safetynet"?
Click to expand...
Click to collapse
Certification for google services and other apps that require a certified device.

Very helpful! Can you make another tutorial about how to debloat manually and which apps we'll should debloat? Thanks.

Fox-guy said:
Very helpful! Can you make another tutorial about how to debloat manually and which apps we'll should debloat? Thanks.
Click to expand...
Click to collapse
I will work on that.

Heads up, im retiring my A70 as i bought an S21 5G. This means I can do more flashing, testing and building on the A70 without the worry of loosing my daily driver in which my lifestyle requires. Im no expert so be patient please and don't expect a first release anytime soon.

hello! does it work with SM-A705MN ? thanks a lot!

HI,
so i follow your guide but stuck on install DFE. i complete flash twrp and sucessfully boot to it. But, it doen't recogin my internal store. and my pc not recogin my phone via twrp too. So i can't flash anything. ( i don't have SD card ). A way to fix it?

mrttd said:
HI,
so i follow your guide but stuck on install DFE. i complete flash twrp and sucessfully boot to it. But, it doen't recogin my internal store. and my pc not recogin my phone via twrp too. So i can't flash anything. ( i don't have SD card ). A way to fix it?
Click to expand...
Click to collapse
After install of twrp and boot to it, you need to format data... Click wipe, advanced wipe, format data, type yes then click blue check mark lower right corner. Reboot to recovery then you can flash DFE then format data again and reboot to system.

Perfect guide, simply, easy and working!

I faced a weird problem. My touch stopped working after installing TWRP, so I could not perform Step 6.
Solution to this: Connect an external mouse to your device via an OTG connector and use it as a pointing device to perform the rest of the steps on TWRP.
Cheers,
Amey

ameyanekar said:
I faced a weird problem. My touch stopped working after installing TWRP, so I could not perform Step 6.
Solution to this: Connect an external mouse to your device via an OTG connector and use it as a pointing device to perform the rest of the steps on TWRP.
Cheers,
Amey
Click to expand...
Click to collapse
That should not happen, is the device updated to latest Android and did you use twrp i provided or a different one?

MarvinMod said:
-WARNING-
THIS IS FOR THE SAMSUNG GALAXY A70 VARIANTS ONLY. THE INTERNAL STORAGE WILL BE WIPED AND DATA WILL BE LOST, PLEASE MAKE A BACKUP BEFORE CONTINUING. I AM NOT RESPOSIBLE FOR BRICKING, FOLLOW THIS GUIDE EXACTLY, DO NOT SKIP STEPS. You will need a Data/WiFi connection.
PC tools/files are linked at bottom of guide.
Unlocking the Bootloader
1- Make sure your connected to data or wi-fi. Open settings, Click about phone, Software Information, Keep tapping Build number till you see Developer options have been enabled message. Click back, back, Developer options, turn on oem unlocking, power off the device.
2- Press and hold vol up and vol down, Plug in usb cable from pc and let go when you see the WARNING screen, press and hold vol up till the unlock bootloader screen, press vol up for yes.
3- The device will now factory reset and reboot. congrats, you've unlocked the bootloader.
Custom Recovery (TWRP)
Recovery.tar-
recovery.tar | by MarvinMod for Galaxy a70
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
D.F.E.-
DFE.zip | by MarvinMod for Galaxy a70
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
1- Make sure you have updated your Device to the latest Android operating system Android 11 one UI 3.1 and use odin 3.13.3
2- Download Recovery.tar and D.F.E. listed above, ( Recovery has vbmeta packed in, so its just a single flash. ) Boot to Android and Make sure Developer options is enabled and oem unlock is toggled on.
3- Unplug from PC and Power off the device. Once powerd off, Hold vol up and vol down, Plug into PC, let go when you reach the bootloader warning screen and press vol up
4- On your PC open odin, click options and uncheck auto reboot, click Log, click AP, select the recovery.zip file, click start. Wait for Pass.
5- Press and hold vol down and power till the screen turns blank then immediately press and hold vol up. The device will reboot then land you in the twrp splash screen
6- Slide right to allow modifications, Click Wipe, Format Data, Type yes then click the blue check in lower left corner. Click back, back, Reboot, recovery
7- Slide right to allow, Connect to the PC and copy the D.F.E. file over. Click install, select the D.F.E file, slide right to confirm flash
8- Click back, back, wipe, Format Data, Type yes then click the blue check in lower left corner.
9- Click Reboot System and setup device. Congrats, you now have Custom Recovery TWRP.
Root with Magisk
Magisk v24.3-
Magisk-24.3(24300).zip | by MarvinMod for Galaxy a70
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
1- Unplug from PC and power off the device. Plug into PC and Device. When is starts charging, Press and hold vol up and power till the device boots. You should now be in TWRP
2- Slide right to modify, Copy Magisk v24.3 to Device, Click install, Select Magisk, Slide right to Flash, Click reboot to system.
3- Open you app drawer and wait for Magisk app to appear. Wala, your now Rooted with Magisk.
Passing Safety Net
Safetynetfix- https://androidfilehost.com/?fid=2981970449027573706
MagiskHideProps- https://androidfilehost.com/?fid=2981970449027573707
YASNAC- https://androidfilehost.com/?fid=2981970449027573708
1- Copy Safetynetfix, MagiskHideProps and YASNAC to Device
2- Open Magisk, Click setting, Enable Zygisk, Reboot
3- Open Magisk and click Modules, Install from storage, select safetynetfix, reboot
4- Open Magisk and click Modules, Install from storage, Select MagiskHideProps, reboot
5- Open File browser and install YASNAC App, Check Assertation for Safety net Pass.
Toolz
Downloads for : Samsung Galaxy a70 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Custom Roms
1- will add when an actual stable working Rom is available. 4/8/2022
Click to expand...
Click to collapse
Finally I have installed tWRP Recovery ...I just want to ask you a question ...If I want to go to tWRP recovery again, what combination key by pressing which I will go to tWRP recovery mode?

Related

[TUTORIAL][ROM] How to fix your phone and apply the update

I have talked to many people that had issues applying the OTA update. Here are the steps to get your phone back to stock and apply the update.
As always, I'm not responsible for anything. yadda yadda.
First, download http://www.multiupload.com/NMPX3KMWRS
This contains Odin, the Samsung Drivers, stock odin rom, updated odin rom, pit file.
If you don't want to lose your settings, etc. you can skip to the second part. If your phone still doesn't work than start from the top.
-PART 1-
Step 1.) Make sure you have the appropriate drivers installed for your phone. If you are on 64bit then choose 64, if you are on 32 choose 32. You may already have the drivers installed and it will tell you after you try to install them.
Step 2.) Power your phone off
Step 3.) Open Odin.exe and plug a usb cable to your computer that will connect to your phone (do not plug it in to the phone yet, just the computer)
Step 4.) Hold down both volume buttons at the same time and while holding them down plug the usb into your phone. You should see a COM message show up in Odin.
Step 5.) To ensure your phone is back to stock, in odin you will want to check the repartition button. ONLY CHECK IT WHEN YOU ARE FLASHING BACK TO STOCK. Leave the other check boxes the way they are.
Step 6.) Click the PIT button and select the 512.pit file
Step 7.) Click the PDA button and select Original.tar and then click Start
It should go through a bunch of steps and then your phone will reboot. Below are the steps to update it to the latest release.
Close Odin and power your phone off.
-PART 2-
Step 1.) Open Odin.exe and plug a usb cable to your computer that will connect to your phone (do not plug it in to the phone yet, just the computer)
Step 2.) Hold down both volume buttons at the same time and while holding them down plug the usb into your phone. You should see a COM message show up in Odin.
Step 3.) Leave all check boxes the way they are. Do NOT check the repartition box.
Step 4.) Click the PIT button and select the 512.pit file
Step 5.) Click the PDA button and select T959UVJI6.tar and then click Start
It will go through a bunch of steps and then your phone will reboot. Congrats, you are on the latest update!
This should be stickied in general so the whole first page isn't taken up with topics about being soft bricked.
When you say updated odin rom, is this the official updated ota that its rolling out now?
Sent from my SGH-T959 using Tapatalk
Beautiful. Thank you for the post. Will do this later tonight and update the sticky in general. Thank you!
I assume with this method you lose your apps and settings? That's not the case with the ota... I could be wrong.
will this work on a hardware lock phone?
s15274n said:
Beautiful. Thank you for the post. Will do this later tonight and update the sticky in general. Thank you!
I assume with this method you lose your apps and settings? That's not the case with the ota... I could be wrong.
Click to expand...
Click to collapse
You are correct - the fix with the repartition will wipe all your data, but it actually should not be necessary to flash back to the stock ROM. We resolved this problem on the main thread for this issue earlier today by just using ODIN 1.3 to flash to the JI6 ROM directly. This approach saves all user data and restores the phone directly to the new version without losing any user settings or data.
Edit:
The older thread is here: http://forum.xda-developers.com/showthread.php?t=802828
The solution we found is pretty much identical to the final 5 steps above in the OP post - many of us have executed just those steps to restore without reverting to stock and without losing user data.
Edit 2 - Thanks youneek for updating the instructions with this option
Can I flash over J14 or do I need to revert to stock?
Thank you for this thread. I was able to revert back to stock and flash JI6. I know that it wasn't necessary to go back down to stock but I just wanted to start everything over. It went very smoothly, I actually did it while I was sitting in my night's class lol.
How long?
How long should it take for the first Odin cycle - returning to stock - to take?
Odin 3.1 has been running for at least 15 minutes. ID: COM shows as 0:[COM6]. PIT and PDA are appropriate. The Odin message area reads:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
Everything for me took less than 5 minutes.
Sent from my SGH-T959 using XDA App
RebDovid said:
How long should it take for the first Odin cycle - returning to stock - to take?
Odin 3.1 has been running for at least 15 minutes. ID: COM shows as 0:[COM6]. PIT and PDA are appropriate. The Odin message area reads:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
Click to expand...
Click to collapse
Entire Odin took me less than 5 minutes last time I did it.
This happened to me the first time I odin'd my phone .... I restarted the phoen and got the Phone--PC error. Just get back to download mode & restart the flash, should work next time through.
Considering what Odin does, it is a very buggy program and is prone to crashes.
Thank you
Easy, breezy, beautiful !!!
The update doesn't wipe the data if you had a stock ROM before that. All my apps and settings are intact after the installation just perfect...
Just have a question: is it ok to root the phone with one-click-root?
Thanks again...
kangxi said:
Everything for me took less than 5 minutes.
Click to expand...
Click to collapse
So, if I need to try again, what do I do (besides not turning off my Vibrant)?
I've done the update but now when I try to root the phone again, I get a 'E:cannot open /sdcard update.zip (No such file or directory)' now when I choose re-install packages. I've tried the one click root apk method and the update.zip placed in the directory manually. Nada. Whats the deal?
My directories are labeled D and F when mounted on my pc if it means it's looking for it in E now...
RebDovid said:
So, if I need to try again, what do I do (besides not turning off my Vibrant)?
Click to expand...
Click to collapse
Just put your phone back into download mode and try again.
Sent from my SGH-T959 using XDA App
one-click-root
Nokternal said:
I've done the update but now when I try to root the phone again, I get a 'E:cannot open /sdcard update.zip (No such file or directory)' now when I choose re-install packages. I've tried the one click root apk method and the update.zip placed in the directory manually. Nada. Whats the deal?
My directories are labeled D and F when mounted on my pc if it means it's looking for it in E now...
Click to expand...
Click to collapse
I just rooted with one-click-root.. no problems here.. disregard the question from my previous post.
I just enabled usb debugging, connected the phone, started one-click-root and the phone rebooted... then "reinstall packages" and the phone came back rooted...
Can't access LBSTestMode menu from *#*#1472365#*#* anymore...any idea?
i just tried this and odin is stuck and has not done anything the message area say this please help
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.rfs
Hi all,
I've read almost every post about the update, but still have some questions so here goes.
I'm on complete stock, untouched. didn't even install clockwirkmod recovery. The ONLY thing I did was root.
I'm out of the US so obviously no OTA for me.
I was wandering if I need to unroot inorder to use the Odin method and wether it is possible to reroot after. Does the update break root, does it have any this to do with it?
Also, is flashing clockwork rec risking anything? Afterall I understand I have to nandroid backup so I need it right?
Thx
BTW, this is my first post (noob) so will be happy to get a bit more than the common nutshell answer since I'm new
Sent from my SGH-T959 using XDA App
i followed these steps but i can't make my phone go into download menu. damn it! the ota taking too long to arrive.
OMG!
This fix the phone!
My phone was bricked by OTA and this method DOES recover my phone back to normal. I could even recover my important DATA!
PS. T-mobile can't recover my data.
Thank you superman in XDA.

P7310 Soft Brick??

So I just bought a Samsung Galaxy Tab 8.9 off craigslist. The guy had 4.1 loaded on it and it's rooted w/ Rom manager installed + clockwork recovery. I downloaded some the stock roms, and put it into the root folder. I then went into Rom manager and clicked boot into clock recovery. My tablet reboot, then after the Galaxy Tab 8.9 logo appear, it shuts off the screen. I can get into the boot mode w/ the 2 options, install factory or download mode. However, if I choose either one, it'll go into a gray screen, then shuts off. Is my tablet now just paperweight? :crying:
[edit]
I just realized I can get into ODIN3 Download Mode, but I don't know what to do from there.
It happen to me yesterday i solved the problem with flashing again the clockworkmod 5.4.4 with odin through pc, hope this is helpful
Edit
I cannot post video but search on YouTube 'install cwm galaxy tab p7310 8.9' it will guide you step by step, you cant miss it xD
If you can get into download mode then use pc odin to flash the stock rom. Install samsung kies(this is only for installing samsung drivers)Open the pc odin and choose the button written pda if your downloaded stock Rom is single md5 file or else if you have multiple file then choose for each one eg "kernel, phone,csc etc...".after doing this put your tab into download mode and connect it to the usb data cable, now your odin com area should turn yellow. Dont check any extra boxes rather then the one already checked in odin. Now press flash, wait for a while and let the computer do the flashing. After you finish flashing factory reset it once before using.
Next time give a little time in research before flashing your rom. Best of luck
Sent from my GT-N7000 using xda app-developers app
chucky5455 said:
If you can get into download mode then use pc odin to flash the stock rom. Install samsung kies(this is only for installing samsung drivers)Open the pc odin and choose the button written pda if your downloaded stock Rom is single md5 file or else if you have multiple file then choose for each one eg "kernel, phone,csc etc...".after doing this put your tab into download mode and connect it to the usb data cable, now your odin com area should turn yellow. Dont check any extra boxes rather then the one already checked in odin. Now press flash, wait for a while and let the computer do the flashing. After you finish flashing factory reset it once before using.
Next time give a little time in research before flashing your rom. Best of luck
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes, I downloaded a stock rom that has the same version as my galaxy tab box. It has been running for 20 minutes already, but it hasn't moved in a while. Below is a log. I downloaded UEKHA version.
Code:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7310XARKHA_P7310UEKHA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img.md5
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.md5
<ID:0/004> hidden.img.md5
<ID:0/004> recovery.img.md5
<ID:0/004> system.img.md5
After spending hours, literally almost not sleeping. Then I woke up and fixed it on the spot.
1. Install Odin 1.85 on the computer
2. Download ClockWorkMod (CWM - get latest version or something)
3. Run Odin (select PDA and select the ClockWorkMod.tar file)
4. Get into recovery mode (volume down + power)
5. Once it gives 2 choices, choose Download.. Press Volume Up, then Volume Up again until the screen goes to telling to plug in the USB. Make sure the Samsung Kies tray agent is disable (control alt delete and end the tray agent process)
6. Plug in the USB, and click start. It should be a 6 seconds process to complete.
7. Once the device is rebooted. Get back into recovery mode.
8. This time, select the first option (factory reset), and it'll go into CWM
9. Once in CWM, clear all the settings (even the advance settings).
10. Make sure the e-sign toggle is off
11. Now you can either run your backup recovery that your device made (if you had CWM running before) or install stock rom from SD card.
I happened to have a stock rom in my device, so I selected that. It gave me an error because it was detecting the esignature so I had to toggle it off, and selected stock rom again. This time, it was a miracle, it worked!!
I still cant get mine to unbrick
detectiveloki said:
After spending hours, literally almost not sleeping. Then I woke up and fixed it on the spot.
1. Install Odin 1.85 on the computer
2. Download ClockWorkMod (CWM - get latest version or something)
3. Run Odin (select PDA and select the ClockWorkMod.tar file)
4. Get into recovery mode (volume down + power)
5. Once it gives 2 choices, choose Download.. Press Volume Up, then Volume Up again until the screen goes to telling to plug in the USB. Make sure the Samsung Kies tray agent is disable (control alt delete and end the tray agent process)
6. Plug in the USB, and click start. It should be a 6 seconds process to complete.
7. Once the device is rebooted. Get back into recovery mode.
8. This time, select the first option (factory reset), and it'll go into CWM
9. Once in CWM, clear all the settings (even the advance settings).
10. Make sure the e-sign toggle is off
11. Now you can either run your backup recovery that your device made (if you had CWM running before) or install stock rom from SD card.
I happened to have a stock rom in my device, so I selected that. It gave me an error because it was detecting the esignature so I had to toggle it off, and selected stock rom again. This time, it was a miracle, it worked!!
Click to expand...
Click to collapse
Hi, I followed this and it seemed to work up until line 8 - CWM doesnt appear - I kept getting a message - /cant access to ‘system/csc
/XEF/system/ What does that mean? Help I'm desperate I only got my tab last week and I've bricked it already!!!!!:crying:
MikeMcGrathXmen said:
Hi, I followed this and it seemed to work up until line 8 - CWM doesnt appear - I kept getting a message - /cant access to ‘system/csc
/XEF/system/ What does that mean? Help I'm desperate I only got my tab last week and I've bricked it already!!!!!:crying:
Click to expand...
Click to collapse
I think you should flash a stock rom with odin first and after put the recovery, that work on mine !
which exact model do you have?
There are many ways to do it, but I used CWM on mine because Odin wasn't working for some odd reason. I left Odin to flash my stock rom overnight and it hung when I woke up in the morning, hence why I used CWM. You can use Odin to flash CWM into your tablet. The only down part is that in order to use CWM, you have to have a ROM backed up in your tablet (Luckily I had a stock rom backed up).

[Q] Can´t restore recovery / adb / SD not recognize

Hi!!
First, I was trying to find some solution, here and google, but every one that could work, don´t.
I was trying to install CyanogenMod 10.1
I followed the installation guide... but when I have to choose CM zip file, I choosed another one from other sell (I was using the same card)
The CM that I use was this: cm-7.2.0-jordan.zip (from a defy phone)
instead cm-10.1-20130621-NIGHTLY-janice.zip
Everything goes bad since that.
I tried to wipe data/factory reset:
E: format_volume: fs_type "ext3" unsupported
E: Can´t mount /cache/reovery/log
E: Unknow fs_type "ext3" for /cache
I tried to update from external storage
But only shows me this: " ../ "
I tried to apply update from ADB
I followed the guide, copy the roms on self directory, put the 4 files on c:\windows , etc.
This are the common errors that shows me:
C:\Windows\Herramientas Sideload>adb sideload gapps-jb-2013
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
I tried kill the adb.exe like this, but doesn´t works
error: closed adb
I tried this but doesn´t works
I found nothing that could help more, so that´s way I making this post.
Here is some data:
GT-i9070
Windows 7 64bits
Kies updated (but could connect to the device now)
I think that drivers of the cell are updated, because windows shows me that... buy i don´t know if is the correct one.
I will be very grateful if you can help. I hope this can be fixed ..
Best regards!!
PS: sorry my english.
Can you enter in download mode with vol down+home+power when phone is switched off?
I didn´t know that.
Yes, now is in downloading mode:
Do not turn off target.
My pc can´t recognize it
Mr.BUBU said:
I didn´t know that.
Yes, now is in downloading mode:
Do not turn off target.
My pc can´t recognize it
Click to expand...
Click to collapse
Reflash stock jelly bean with Odin, then flash CoCore kernel for CWM recovery, and retry to flash CM10.1. To do that:
1-Because your pc doesn't recognize the device uninstall Kies and install only usb drivers (you can download install package here)
2-Download Odin and i9070 Stock Jelly Bean firmware from samfirmware (I recommend i9070XXLQG PDA)
3-Extract downloaded zip, you will find three files (one .dll, one .pit and one .tar.md5)
4-Launch Odin, select "Re-Partition" and leave others as they are. Press "PIT" button and select .pit file in extracted firmware's zip file, then press "PDA" and select .tar.md5 file in same directory.
5-Enter in download mode like I said you early and connect device to pc, press "Start" button on Odin and wait for the "SUCCESS" message, now your phone should power on normally.
6-Now download this zip file (for obtain root access) and put in sd card (micro sd, not internal memory!)
7-Turn off your phone, press vol up+home+power to enter recovery, select "apply update from external storage" then select root.zip, reboot device.
8-Now you have stock jelly bean rooted, update SuperSU from Google Play and install Universal Kernel Flash from frapeti (you can find it on Play Store).
9-Download CoCore Kernel here, take kernel.bin.md5 file from zip package and put it in internal storage.
10-Launch Universal Kernel Flash, select kernel.bin.md5 and flash it.
11-Power off phone and enter again in recovery with vol up+home+power, now you should have CWM-based recovery, select "backup and restore" and take a full system backup.
12-Wipe data, cache and dalvik and retry to install CM10.1-janice, in case something goes wrong or you want to remove CM without flash again with Odin you can restore your system backup from CWM.
If you have a doubt I'm here to help you
Problem:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9070XXLQG_I9070OXXLQG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
8(
There wasn´t a .pít file on the i9070XXLQG
I found one from Odin3-v1.85.zip
Could be that why is wrong? I´m downloading one more... this time without the Kies sign. I bet that is the probelm.
it´s getting worst
Now when I turn on the phone, the screen looks with diagonals strips.
And only the download mode is working... no more for upload mode.
:crying:
Well... i was looking for that error... and could be the cable and the usb port.
I changed each one, and still don´t works.
Remove the SD, remove the sim, and every time get me the same error.
Anything else?
Which .pit you have? The name of the correct one is: GT-I9070_EUR_XX_8G.pit for 8GB memory. Your have 8GB or 16GB of memory?
This one, but it came with the odin... I think.
u1_02_20110310_emmc_EXT4.pit
I will look for the correct one :good:
Mr.BUBU said:
This one, but it came with the odin... I think.
u1_02_20110310_emmc_EXT4.pit
I will look for the correct one :good:
Click to expand...
Click to collapse
Always use specific pit file of a device, each Samsung device have it, for example I can't use i9000's pit file on i9070. Which model is? 8 or 16? Because the two models have different pit file
Now I know...
8gb model.
Mr.BUBU said:
Now I know...
8gb model.
Click to expand...
Click to collapse
Okay, the correct file is the one that I said you, you can find it here on xda or with Google, I have it on pc (I'm writing with phone) but here in Italy is too late and I'm going to sleep if you can't find it I can upload it for you
THANKS YOU
THANKS YOU
THANKS YOU
THANKS YOU
THANKS YOU
THANKS YOU
:laugh:
It´s alive !!!
And with CyanoGen working
I had to avoided some steps, because no one version let me get in the Os. Every each stop working when complete the time of the cell. Never been able to install Super Su for example.
So... I take the CM janice and the gapps cyano and at least is working. :victory:
Now to test and re test... before installing everything else.
Thanks you so much. I was affraid to had broke the cell for ever.
You really known about this... thanks for help me :good:
Mr.BUBU said:
THANKS YOU
Click to expand...
Click to collapse
next time, don't mix up the devices, files or steps. then you'll be fine.
Sent from a rice cooker
Mr.BUBU said:
THANKS YOU
THANKS YOU
THANKS YOU
THANKS YOU
THANKS YOU
THANKS YOU
:laugh:
Click to expand...
Click to collapse
Excellent, next time be careful when you're flashing roms
Thanks for the advice harith.unnikrishnan and Tesla-MADAL93
I have root some, but never flash roms. Always there is a first time... in my case was catastrophic
Best regards!!
Mr.BUBU said:
Thanks for the advice harith.unnikrishnan and Tesla-MADAL93
I have root some, but never flash roms. Always there is a first time... in my case was catastrophic
Best regards!!
Click to expand...
Click to collapse
Don't worry, the important is that now it works
Mr.BUBU said:
Thanks for the advice harith.unnikrishnan and Tesla-MADAL93
I have root some, but never flash roms. Always there is a first time... in my case was catastrophic
Best regards!!
Click to expand...
Click to collapse
It was not catastrophic. It would be if you flashed wrong firmware with Odin. :silly:
shut_down said:
It was not catastrophic. It would be if you flashed wrong firmware with Odin. :silly:
Click to expand...
Click to collapse
I agree with you, shut_down

[Q] Help me please

Hello new in this forum.....
The threads I read overwhelmed me.... :cyclops:
I have a N7000 from a friend of mine. It had a dedicated 4.0.4 rom from "3" (italian operator) build IMM76D.XXLRL
I tried to install a new italian rom 4.1.2 via odin but every attempt failed
Unfortunately I ended up into a thread about ICS kernel (sorry if I make some mistakes with names but I'm really lost....)
so downloaded the ICS and with my surprise it was installed into the phone.
From that moment the N7000 hang at samsung logo with the yellow triangle....
And the worst thing It goes in download mode but not in recovery mode.....
I tried to read many post before write, trying to understand waht to do but now I'm totally confused..... md5,tar,img, zip...... kernel,root, cwm., rom ....
Someone may explain to me if there is something to do to save the phone?
Thanks i n advance
Andrea
andrew59it said:
Hello new in this forum.....
The threads I read overwhelmed me.... :cyclops:
I have a N7000 from a friend of mine. It had a dedicated 4.0.4 rom from "3" (italian operator) build IMM76D.XXLRL
I tried to install a new italian rom 4.1.2 via odin but every attempt failed
Unfortunately I ended up into a thread about ICS kernel (sorry if I make some mistakes with names but I'm really lost....)
so downloaded the ICS and with my surprise it was installed into the phone.
From that moment the N7000 hang at samsung logo with the yellow triangle....
And the worst thing It goes in download mode but not in recovery mode.....
I tried to read many post before write, trying to understand waht to do but now I'm totally confused..... md5,tar,img, zip...... kernel,root, cwm., rom ....
Someone may explain to me if there is something to do to save the phone?
Thanks i n advance
Andrea
Click to expand...
Click to collapse
so, what is your question actually??
Mate, I think the question is simple.
From what I understand in your comment, it seems you tried to install the Stock Rom 4.1.2 Italy, when you were the 4.0.4 / 4.0.3 Stock Rom Italy. On installation through ODIN pc you had a problem where it remains in the Samsung logo, will not let you enter the Recovery mode, only the Download mode. Is that so?
I should arrived that case do not leave any triangle would remove the battery, and after 10-15 seconds reintroduce it, and just then press buttons to enter the Recovery mode. If it fails, repeat the removal of the battery, but now when placed connect the DC charger to the phone I tried to turn normally to 20-25 seconds (just outside and away the logo of battery charging), and try to turn it on Recovery mode again, but we will keep down so long that should disappear all as to turn it off, and you press the keys for the Recovery mode, this time releasing anything else lighting appear on the screen, just a moment before letters GT-N7000, now if it really is accessible Recovery should apparate.
If you enter Recovery Mode Stock Samsung, you will have look out if a line appears below indicating the application, or wondering whether to apply the new CSC, we accept without thinking, since it must reaffirm the phone to initiate a Stock Rom.
Now if I come to this moment really was not accessible Recovery mode should get a screenshot of ODIN pc which finishes entering files to mobile, if it were really a fault, and do not leave do the installation, if you checked any box incorrectly, of which are not activated.
Other options include USB cable failure, USB port, lack of USB debugging enabled before starting the installation, do not put at least 10 minutes in the backlight time (this can try to fix running a finger across the screen every 23 seconds if it was 30 seconds off), but that the capture can determine ourselves if the error is only for ODN pc, which can be a failed in the installation and have not really finished the installation, in this case it would be almost insurance problem USB cable used, and in extremis or USB port.
fusionero said:
Mate, I think the question is simple.
From what I understand in your comment, it seems you tried to install the Stock Rom 4.1.2 Italy, when you were the 4.0.4 / 4.0.3 Stock Rom Italy. On installation through ODIN pc you had a problem where it remains in the Samsung logo, will not let you enter the Recovery mode, only the Download mode. Is that so?
I should arrived that case do not leave any triangle would remove the battery, and after 10-15 seconds reintroduce it, and just then press buttons to enter the Recovery mode. If it fails, repeat the removal of the battery, but now when placed connect the DC charger to the phone I tried to turn normally to 20-25 seconds (just outside and away the logo of battery charging), and try to turn it on Recovery mode again, but we will keep down so long that should disappear all as to turn it off, and you press the keys for the Recovery mode, this time releasing anything else lighting appear on the screen, just a moment before letters GT-N7000, now if it really is accessible Recovery should apparate.
If you enter Recovery Mode Stock Samsung, you will have look out if a line appears below indicating the application, or wondering whether to apply the new CSC, we accept without thinking, since it must reaffirm the phone to initiate a Stock Rom.
Now if I come to this moment really was not accessible Recovery mode should get a screenshot of ODIN pc which finishes entering files to mobile, if it were really a fault, and do not leave do the installation, if you checked any box incorrectly, of which are not activated.
Other options include USB cable failure, USB port, lack of USB debugging enabled before starting the installation, do not put at least 10 minutes in the backlight time (this can try to fix running a finger across the screen every 23 seconds if it was 30 seconds off), but that the capture can determine ourselves if the error is only for ODN pc, which can be a failed in the installation and have not really finished the installation, in this case it would be almost insurance problem USB cable used, and in extremis or USB port.
Click to expand...
Click to collapse
Thanks to reply.....
I was not really clear probably.
I tried to install 4.1.2 over 4.0.4 dedicate rom (3 H3G italian operator)
Odin always failed hanging or giving some fault
So I installed the ICS kernel (or rom) everything was fine. So I suppose the cable is ok , odin is ok etc....
But from the moment I downloaded the ICS, at reboot the phone hang on samsung logo with yellow triangle. ANd if I try to switch off the phone it restart and hang on logo.
Download mode is still working but recovery mode not.....
I'm looking for some kernel, rom, cwm to download, to recover the phone.....
The best thing to do is reinstall the ROM 4.1.2 (the 4.0.x are more dangerous if we wipes, JellyBean when they are not), but check that no error appears, if it appears only after installing the Rom rather fails during it, you can download the kernel Philz for you version, right now if you tell me the link to SamMobile I can tell you what, so you can tell which is correct, although it is not hard to tell if you look at the post of Philz above kernel with all links to them. After installation and download the kernel, you turn the phone into Recovery mode, you select mount usb (I think it came out well, but stresses) and connect your phone to your pc, you can pass the kernel to the internal SD and another copy to the SD external (remember to leave both copies at the root of both SD's). You MUST complete the transfer and disassemble with the option displayed on screen, and disconnect the USB cable. You continue by going to install zip, and should be able to select the Kenel Philz to install, after installing (if you get an error: Status 7 quiet, it was not the correct version of the kernel, and not actually installed), you will have to restart the mobile again, but when you start on with the letters GT-N7000, you will have to restart it by pressing Vol + - Power - Home, all at once, and keep it until the letters again, and keep it until it goes - restart, then you press the 3 keys, and when the letters appear, you must drop the 3 keys, and should you appear the menu Recovery kernel Phliz, there as you will see below something that says CSC implemented or instead ask if you want to apply, accept if you ask, and you should be able to restart the phone and wait about 5 minutes maximum to emit sound and vibration as it is booting at all, and then you should be able to start getting bills from Samsung and Google.
Thank fusionero
the problem is I'm not able to install the 4.1.2 , odin hang or fail
The ROM version I need is
sammobile.com/firmwares/download/22314/N7000XXLT9_N7000ITVLT3_ITV
So I think nex step is to install kernel Philz but I don't know which version I need. On the phone was installed 4.0.4 build IMM76D.XXLRL
CIAO
You must enter this http://www.sammobile.com/firmwares/download/22314/N7000XXLT9_N7000ITVLT3_ITV.zip/ address, and you must connect to you account to download that version you mention, I just check and this downloading smoothly on my pc . The problem is that it would open without ending .zip or you caught hours of server failure, just that i found this morning when downloading another who asked me.
As to what you mention about the version you have installed, as you are looking at the correct thread ( http://forum.xda-developers.com/showthread.php?t=1901191 ), the kernel you need for what you indicate ( 4.0.4 build IMM76D.XXLRL CIAO ) is this:
Update to all ICS 4.0.4 kernels from 3.71 ---> 3.99:
http://www.mediafire.com/?3ale6m9q6b6a3
Updated kernels list:
PhilZ-cwm6-BULR1-SWC-v3.99
PhilZ-cwm6-DDLR6-ODD-v3.99
PhilZ-cwm6-DDLR9-INU-v3.99
PhilZ-cwm6-DDLRB-ODD-v3.99
PhilZ-cwm6-DXLP9-OLB-v3.99
PhilZ-cwm6-DXLR2-OLB-v3.99
PhilZ-cwm6-DXLR5-OLB-v3.99
PhilZ-cwm6-JPLPD-OJP-v3.99
PhilZ-cwm6-JPLR8-OJP-v3.99
PhilZ-cwm6-UBLPC-UUB-v3.99
PhilZ-cwm6-UBLR3-PSN-v3.99
PhilZ-cwm6-UBLR5-TCE-v3.99
PhilZ-cwm6-XXLPY-XEN-v3.99
PhilZ-cwm6-XXLQ3-OXX-v3.99
PhilZ-cwm6-XXLRG-DBT-v3.99
PhilZ-cwm6-XXLRI-AUT-v3.99
PhilZ-cwm6-XXLRK-XEU-v3.99
PhilZ-cwm6-XXLRL-HUI-v3.99 - Is this your kernel
PhilZ-cwm6-XXLRQ-DBT-v3.99
PhilZ-cwm6-XXLRT-DBT-v3.99
PhilZ-cwm6-XXLRU-VDI-v3.99
PhilZ-cwm6-XXLRW-SFR-v3.99
PhilZ-cwm6-ZSLPF-OZS-v3.99
PhilZ-cwm6-ZSLPM-OZS-v3.99
PhilZ-cwm6-ZSLPN-OZS-v3.99
Click to expand...
Click to collapse
andrew59it said:
Hello new in this forum.....
The threads I read overwhelmed me.... :cyclops:
I have a N7000 from a friend of mine. It had a dedicated 4.0.4 rom from "3" (italian operator) build IMM76D.XXLRL
I tried to install a new italian rom 4.1.2 via odin but every attempt failed
Unfortunately I ended up into a thread about ICS kernel (sorry if I make some mistakes with names but I'm really lost....)
so downloaded the ICS and with my surprise it was installed into the phone.
From that moment the N7000 hang at samsung logo with the yellow triangle....
And the worst thing It goes in download mode but not in recovery mode.....
I tried to read many post before write, trying to understand waht to do but now I'm totally confused..... md5,tar,img, zip...... kernel,root, cwm., rom ....
Someone may explain to me if there is something to do to save the phone?
Thanks i n advance
Andrea
Click to expand...
Click to collapse
Your phone is not booting since you flashed an ICS kernel over a JellyBean ROM
Android ICS version : 4.0.4
Android JB version : 4.1.2
so I hope you understand the difference.
You are lucky you didn't brick your device or have you already
But since you are able to go in download mode I think its not bricked yet.
It was probably a bad download which failed the installation so download ROM again and this time verify that your download is not corrupt by running it via md5 if provided.
also please provide the link of the ROM thread that you are trying to install so that I can understand better
and if you are not looking to flash a custom ROM or rooting your device in order to do so then in that case the steps are pretty straight forward
download Stock ROM
extract ROM
open Odin
select appropriate files i.e Choose CODE in PDA, MODEM in PHONE, Multi CSC in CSC
put phone in download mode and connect
the bar should turn yellow once connected.
once connected click on flash
bar should turn green if successful
REVENGE SOLVES EVERYTHING
tysonraylee said:
Your phone is not booting since you flashed an ICS kernel over a JellyBean ROM
Android ICS version : 4.0.4
Android JB version : 4.1.2
so I hope you understand the difference.
You are lucky you didn't brick your device or have you already
But since you are able to go in download mode I think its not bricked yet.
It was probably a bad download which failed the installation so download ROM again and this time verify that your download is not corrupt by running it via md5 if provided.
also please provide the link of the ROM thread that you are trying to install so that I can understand better
and if you are not looking to flash a custom ROM or rooting your device in order to do so then in that case the steps are pretty straight forward
download Stock ROM
extract ROM
open Odin
select appropriate files i.e Choose CODE in PDA, MODEM in PHONE, Multi CSC in CSC
put phone in download mode and connect
the bar should turn yellow once connected.
once connected click on flash
bar should turn green if successful
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Thanks everyone....
I think you hit the problem..... but my original ROM version was 4.0.4 .... (H3G)
Anyway probably something went wrong.... I don't need a custom ROM or to root the device.
I need to install N7000XXLT9_N7000ITVLT3_ITV if possible but the flash doesn't start via ODIN
May you explain step by step what have I to do? I really appreciate....
What do you mean "select appropriate files i.e Choose CODE in PDA, MODEM in PHONE, Multi CSC in CSC" ?
md5 is not a single file? I read something about more files to place in odin.....
@ fusionero: I already downloaded the files.... also PHILZ XXLRL but the device doesn't start anyway.....
andrew59it said:
Thanks everyone....
I think you hit the problem..... but my original ROM version was 4.0.4 .... (H3G)
Anyway probably something went wrong.... I don't need a custom ROM or to root the device.
I need to install N7000XXLT9_N7000ITVLT3_ITV if possible but the flash doesn't start via ODIN
May you explain step by step what have I to do? I really appreciate....
What do you mean "select appropriate files i.e Choose CODE in PDA, MODEM in PHONE, Multi CSC in CSC" ?
md5 is not a single file? I read something about more files to place in odin.....
@ fusionero: I already downloaded the files.... also PHILZ XXLRL but the device doesn't start anyway.....
Click to expand...
Click to collapse
Did you download the XXLT9 ROM?? or the ROM that you want to flash ??
if so then it should be a zip file, if you extract that zip file you should have 3 files in it (sometimes only PDA file is present and the other two i.e Modem and CSC are not present, dont worry the PDA file alone is enough)
Open Odin, click on PDA button and select the firmware file with .tar.md5 extension (The firmware file look something like: N7000XXDLJ5_N7000ODDDLI7_INU.tar.md5 Select the one that looks similar to the ROM you downloaded)
and if there are CSC and Modem files then select them by clicking Phone and CSC in Odin accordingly. It will be mentioned in the file name if its a Modem or CSC file
if MODEM_XXXX.tar.md5 then select that file by clicking the PHONE in Odin and if XXXX_CSC_XX.tar.md5 then select it by clicking CSC in Odin
remember that you lose all your data
Then just click flash and it should flash
md5 is a single file and is used to check the integrity of the file you downloaded. Its just used to make sure that the file you downloaded doesnt have any errors or is corrupt. you use the .md5 file and compare it with the md5 of the ROM.zip If it matches then its not corrupted or is a bad download. (.tar.md5 and .md5 are different files as in .tar.md5 is a firmware file and .md5 is a hash file used for integrity check)
Just right-click the rar/zip file and select properties and select the "file hashes" tab and if you downloaded a .md5 open that file by clicking "compare file" in the same tab
.md5 is always provided along with file you downloaded and its size is always in kbs , if its not provided then you cant do the hash check
If you dont have "file hashes" tab after right-clicking and selecting properties of the rar/zip file then you should download and install HashTab to get that option
follow this video for a better understanding https://www.youtube.com/watch?v=Ulz-1UYzHBA
the process is same but you should use your ROM files i.e Italian N7000 files to flash your phone and yes Odin version doesnt matter, you can use any version
Hello
I downloaded N7000XXLT9_N7000ITVLT3_ITV.ZIP
Extracted the file into a folder and had N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar.md5 (there is also SS_DL.dll)
Tried to flash the md5 file with odin (V.1.85) , but odin returns a fail.....
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
andrew59it said:
Hello
I downloaded N7000XXLT9_N7000ITVLT3_ITV.ZIP
Extracted the file into a folder and had N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar.md5 (there is also SS_DL.dll)
Tried to flash the md5 file with odin (V.1.85) , but odin returns a fail.....
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
did you follow the video??
did you select N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar.md5 by clicking PDA??
REVENGE SOLVES EVERYTHING
Yes of course.....
andrew59it said:
Yes of course.....
Click to expand...
Click to collapse
still odin fails?? even after following the video??
are you using the original cable to flash ??
try plugging the cable into a different usb port and flash
Yes it fails
I will try with another cable and port. But if I flash Philz rom it works.....
andrew59it said:
Yes it fails
I will try with another cable and port. But if I flash Philz rom it works.....
Click to expand...
Click to collapse
after trying that try the solution from this post http://forum.xda-developers.com/showthread.php?p=41844601#post41844601
and also try and follow the thread as people have posted different solutions regarding your problem
Also this would be the extent of help i can provide
if that doesnt work i dont know what will
So please forgive me for not being able to help any further :angel:
maybe you should use odin3 v3.04 or v3.09.
usually i use odin3 v1.8X for multiple file roms but in your case, you have only One-file rom.
---------- Post added at 01:12 PM ---------- Previous post was at 01:09 PM ----------
besides, extract all the files in odin archive and place them in one folder dont just start the odin .exe file directly from the archive.
Hello changed the cable the port and ODIN (ver 3.04)
The same problem..... look at the picture attached....
I'm loosing hope.....:crying:
Thanks to all....
solved the problem!!! WOW! :good::victory:
The solution was to change pc, I went on my girlfriend laptop and everything went smooth as silk.....
Thank you all to supporting me !!
andrew59it said:
Thanks to all....
solved the problem!!! WOW! :good::victory:
The solution was to change pc, I went on my girlfriend laptop and everything went smooth as silk.....
Thank you all to supporting me !!
Click to expand...
Click to collapse
congrats
REVENGE SOLVES EVERYTHING

Successfully Unlocked FRP of my SM-T377W from Rogers Canada on 7.1.1

I have successfully Unlocked my SM-T377W from Rogers Canada on 7.1.1
I have been Struggling for a while to Unlock the FRP from this device and finally done it
Now its unlocked and I can use whatever sim card i want also
So I have used these 2 files [IT IS IMPORTANT TO USE THE CORRECT COMBINATION AND CORRESPONDING STOCK], maybe you can use the same ones I have used if you do not have a choice
1- Combination "COMBINATION_OYA_FA60_T377WVLU3ARG1"
2- Stock ROM "Firmware SM-T377W T377WVLU3BRG4 [7.1.1]"
So what I have basically done,
1- Turn the device off and put the device in DOWNLOAD MODE
2- Flash the Combination Firmware to your device with Odin
3- When the device restarts and it runs the Combination firmware, turn it off again and put it in "RECOVERY MODE" not download, and in "RECOVERY MODE" do factory reset wipe and click yes then It will restart or maybe shut off
4- Turn it on again normally and it will run the Combination firmware
5- Now Turn it off again and put in "DOWNLOAD MODE" this time
6- From the Stock ROM extract the 3 files (boot, sboot and system) from inside the files of the stock ROM, you will find them inside "AP" and "BL" (cause we have BL, AP, CP, CSC), you need to use 7-zip so you can extract whats inside them
7- Create new file/archive (it will be .tar) using 7-zip with these 3 files (boot, sboot and system)
9- Flash the new file you made .tar (that has the 3 files) in the AP section in Odin.
10- Your done
Step number 7 where I was struggling before, did not know which files to extract and to flash, but after search/attempts finally I figured it out.
Hope this help
Combination file download
Thank you for giving me hope that I might still get this tablet in usable condition again. I have been looking high and low and tried so many ways to get passed the frp. I've been searching since you sent me your thread but couldnt find a combination file download anywhere that didnt seem suspicious. I have aquired a lot of other tools for later trials but the combination file is still alluding me. Im sure you looked a long time and I know it must be gratifying to have finally gotten yours working. Dont suppose you can share the site you got the file from? Great job btw and a huge thanks for sharing your success as well as inspiration to keep going!
:good::good::good::fingers-crossed::good::good::good:
DaOnlyHihiNalu said:
Thank you for giving me hope that I might still get this tablet in usable condition again. I have been looking high and low and tried so many ways to get passed the frp. I've been searching since you sent me your thread but couldnt find a combination file download anywhere that didnt seem suspicious. I have aquired a lot of other tools for later trials but the combination file is still alluding me. Im sure you looked a long time and I know it must be gratifying to have finally gotten yours working. Dont suppose you can share the site you got the file from? Great job btw and a huge thanks for sharing your success as well as inspiration to keep going!
:good::good::good::fingers-crossed::good::good::good:
Click to expand...
Click to collapse
Combination from here, you will see link down for T377WVLU3ARG1
(Good luck downloading from the site as there are so many Ads, but this is the link i got it from)
Stock Here
(stock easy to find, there are many sites)
Good luck , hopefully it will work
steps above dont seem too work....
are you sure only the 3 files are required in the new .tar?
I can get to step 9 above, but when I try to flash my new .tar file, I get a failed write error right after it tries to write the boot.img file, which is the first file it tries to wrtite.
At this point, I tried just flashing the original 4 files instead, bearing in mind I have already done steps 1-6 successfully, and when the device boots, it is still FRP locked.....
Issue is my ex gfs gmail was the one logged in on my device, i reset before thinking about FRP and now I cant use my device.... Samsung Service Center wants almosts $100 to fx and id rather do it myself because thats crazy considering it should take only 10min if the real process is anything close to this or just uses odin at all.
SpectorOfDeath said:
steps above dont seem too work....
are you sure only the 3 files are required in the new .tar?
I can get to step 9 above, but when I try to flash my new .tar file, I get a failed write error right after it tries to write the boot.img file, which is the first file it tries to wrtite.
At this point, I tried just flashing the original 4 files instead, bearing in mind I have already done steps 1-6 successfully, and when the device boots, it is still FRP locked.....
Issue is my ex gfs gmail was the one logged in on my device, i reset before thinking about FRP and now I cant use my device.... Samsung Service Center wants almosts $100 to fx and id rather do it myself because thats crazy considering it should take only 10min if the real process is anything close to this or just uses odin at all.
Click to expand...
Click to collapse
Then make sure u r using the correct firmware and combination, because if u r not using matched once u will get error
i know the firmware is correct, but how do I know which combination file to use? there is no description of the difference between them or what each is for.....
I have the exact same device as you, just on Bell... I have the 4 full flashing files, bl ap cp csc, and they work fine but dont remove FRP, but they flash and load without issue.... I even have the .pit file just incase, but am not using it as of yet.....
Ive been using the combination fole you noted above, but should I use the other one then? any idea why it would work for you and not me, carrier shouldnt matter in canada now because they are all unlocked anyways
---------- Post added at 08:34 PM ---------- Previous post was at 08:32 PM ----------
do i need to add the param.bin file too ?
---------- Post added at 08:52 PM ---------- Previous post was at 08:34 PM ----------
i just tried the other combination file, and it wont flash like the first one, i gets errors...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 959 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the tablet itself i get the error;
SW REV CHECK FAIL. DEVICE: 3 BINARY: 2
---------- Post added at 09:03 PM ---------- Previous post was at 08:52 PM ----------
maybe this could be it??
I just flash the combination files that you referenced that does flash and boot correctly, and when I get into recovery and do the factory reset in there, I noticed somthing....
this combination file says
Android Recovery
MMB29K.FA60_T337WVLU3ARG1
samsung/gtesltebmc/gtesltebmc
6.0.1/MMB29K/FA60_T337WVLU3ARG1 <<<<----------could this be it?
user/release-keys
I see it says 6.0.1, and im trying to flash 7.1.1 stock afterwards... is that the issue? i need to flash 6.0.1 instead maybe? where can I get the 6.0.1 files as they are not n sammbile firmware
---------- Post added at 09:33 PM ---------- Previous post was at 09:03 PM ----------
no that cant be it, you sad in the begining of the post you used 7.1.1....
so yea, im lost now; I can unpack the BL and AP files and get the 3 files you said together and repack them into a NEW_T337W.tar file with 7zip,
but then i get the get write error in odin when trying to write boot.img and no error shown on tablet
OM*******G --- I GOT THIS TOO WORK FINALLY
just had to take some steps back and think a few things over and try a few things...
I had to alter your instructions abit, but not much, you were bang on for the most part for me....
So what I have done is below, minus the underlined parts, took them out....
---> Good 1- Turn the device off and put the device in DOWNLOAD MODE
---> Good 2- Flash the Combination Firmware to your device with Odin
---> Changed 3- When the device restarts and it runs the Combination firmware, turn it off again and put it in "RECOVERY MODE" not download, and in "RECOVERY MODE" do factory reset wipe and click yes then It will restart or maybe shut off
---> Changed 4- Turn it on again normally and it will run the Combination firmware
---> Good 5- Now Turn it off again and put in "DOWNLOAD MODE" this time
---> ADDED 5.5- RESTART ODIN, not just click restart within Odin, but close and reopen, would not flash the new .tar I make next unless I both skip the factory reset underlinded above && Completely close and reopen Odin
---> Good 6- From the Stock ROM extract the 3 files (boot, sboot and system) from inside the files of the stock ROM, you will find them inside "AP" and "BL" (cause we have BL, AP, CP, CSC), you need to use 7-zip so you can extract whats inside them
---> Good 7- Create new file/archive (it will be .tar) using 7-zip with these 3 files (boot, sboot and system)
---> ADDED 6.5- Make sure Odin has been completed closed and reopened
---> Good 9- Flash the new file you made .tar (that has the 3 files) in the AP section in Odin.
---> Good 10- Your done
Not sure why I had to skip the factory reset as well as restart Odin, I can understand Odin because its a portable version we all use, not system installed, so issues somtimes....
But the factory reset skip was just a tought, that possibly it wouldnt allow me to flash after a factory reset without booting the OS atleast once, and it eneded up being the clintcher for me....
Now there is only one thing I will say about this way to get around FRP, is that you cant preform a factory reset for within the device afterwards, as it re-locks to the old google account again, which means it technically hasnt REMOVED the existing lock, just somehow ignoring the flag. I know this because immediately after I got my .tar to flash and the OS was running and not locked up, I logged into the Play Store and updated play services, and then shut down and I preformed a hard reset within the recovery, just to completely reset the OS one final time and too see what would happen, and it did reformat fine and boot, but was back in its original state, locked to my ex-gfs account, not mine.
SOo I was forced to go thru my steps above again and get back in... worked fine, and I just finshed updateing all my google apps that needed updating in the playstore and seems like everythign is fine, only comes down to not being too factory reset now if I have an issue in the future......
Also brings up my next concern, will I be able to to any future system OTA updates?
I'm not rooted nor do I have any need to be on this device, my LG v30 is rooted already with TWRP, so I havnt broken Knox as far as I know, counter in Download mode is still 0, so Im PRAYING I can do any updates such as those without getting locked out again afterwards....
What I'm hoping, is that over time, what ever 30-90 days, of updates and syncs, that the FRP lock will change to MY google account, not hers, but I have no idea if it will and that only way I can check is to try it in like April, plenty of time and syncing, and see if locks up and I need to do this all over again.
Yea, i was right, OTA updates are broken even with knox at 0x0...
Any idea how long it takes to attach this device to my account over hers?
When/if that happen, you think its better to flash the OS in full back from Odin or just do internal Factory Reset? Wondering if flashing the OS after 72hrs would be more successful in ignoring the old info and grabbing my account since the old info obv hasnt been removed from the device, just ignored by the Combined Firmware Binary
Update: i confirmed this by logging out of all my accounts, samsung google ect, everything and entering Download Mode, should have shown FRP LOCK: OFF but said : ON, which means the device has FRP information still even tho no accounts are logged in and should have released this.
Everything worked as described. If you are finding it difficult to extract and pack the 3 other firmware files, you can opt yo use free tools like Miracle box to load the firmware and then flash only the files you want(sboot, boot, system).
For the link, just indicate and i send it directly to you or visit ifindhub for free Miracle box software.
Patched odin
SpectorOfDeath said:
steps above dont seem too work....
are you sure only the 3 files are required in the new .tar?
I can get to step 9 above, but when I try to flash my new .tar file, I get a failed write error right after it tries to write the boot.img file, which is the first file it tries to wrtite.
At this point, I tried just flashing the original 4 files instead, bearing in mind I have already done steps 1-6 successfully, and when the device boots, it is still FRP locked.....
Issue is my ex gfs gmail was the one logged in on my device, i reset before thinking about FRP and now I cant use my device.... Samsung Service Center wants almosts $100 to fx and id rather do it myself because thats crazy considering it should take only 10min if the real process is anything close to this or just uses odin at all.
Click to expand...
Click to collapse
You may have to use a patched version of Odin, I had issues with this on my Galaxy s9 plus
SpectorOfDeath said:
OM*******G --- I GOT THIS TOO WORK FINALLY
just had to take some steps back and think a few things over and try a few things...
I had to alter your instructions abit, but not much, you were bang on for the most part for me....
So what I have done is below, minus the underlined parts, took them out....
---> Good 1- Turn the device off and put the device in DOWNLOAD MODE
---> Good 2- Flash the Combination Firmware to your device with Odin
---> Changed 3- When the device restarts and it runs the Combination firmware, turn it off again and put it in "RECOVERY MODE" not download, and in "RECOVERY MODE" do factory reset wipe and click yes then It will restart or maybe shut off
---> Changed 4- Turn it on again normally and it will run the Combination firmware
---> Good 5- Now Turn it off again and put in "DOWNLOAD MODE" this time
---> ADDED 5.5- RESTART ODIN, not just click restart within Odin, but close and reopen, would not flash the new .tar I make next unless I both skip the factory reset underlinded above && Completely close and reopen Odin
---> Good 6- From the Stock ROM extract the 3 files (boot, sboot and system) from inside the files of the stock ROM, you will find them inside "AP" and "BL" (cause we have BL, AP, CP, CSC), you need to use 7-zip so you can extract whats inside them
---> Good 7- Create new file/archive (it will be .tar) using 7-zip with these 3 files (boot, sboot and system)
---> ADDED 6.5- Make sure Odin has been completed closed and reopened
---> Good 9- Flash the new file you made .tar (that has the 3 files) in the AP section in Odin.
---> Good 10- Your done
Not sure why I had to skip the factory reset as well as restart Odin, I can understand Odin because its a portable version we all use, not system installed, so issues somtimes....
But the factory reset skip was just a tought, that possibly it wouldnt allow me to flash after a factory reset without booting the OS atleast once, and it eneded up being the clintcher for me....
Now there is only one thing I will say about this way to get around FRP, is that you cant preform a factory reset for within the device afterwards, as it re-locks to the old google account again, which means it technically hasnt REMOVED the existing lock, just somehow ignoring the flag. I know this because immediately after I got my .tar to flash and the OS was running and not locked up, I logged into the Play Store and updated play services, and then shut down and I preformed a hard reset within the recovery, just to completely reset the OS one final time and too see what would happen, and it did reformat fine and boot, but was back in its original state, locked to my ex-gfs account, not mine.
SOo I was forced to go thru my steps above again and get back in... worked fine, and I just finshed updateing all my google apps that needed updating in the playstore and seems like everythign is fine, only comes down to not being too factory reset now if I have an issue in the future......
Also brings up my next concern, will I be able to to any future system OTA updates?
I'm not rooted nor do I have any need to be on this device, my LG v30 is rooted already with TWRP, so I havnt broken Knox as far as I know, counter in Download mode is still 0, so Im PRAYING I can do any updates such as those without getting locked out again afterwards....
What I'm hoping, is that over time, what ever 30-90 days, of updates and syncs, that the FRP lock will change to MY google account, not hers, but I have no idea if it will and that only way I can check is to try it in like April, plenty of time and syncing, and see if locks up and I need to do this all over again.
Click to expand...
Click to collapse
So the file COMBINATION_SPT_FA51_T377PVPU2AQD1_SPTFAC_xxxxxxxxx.tar has these inside it:
aboot.mbn
sbl1.mbn
rpm.mbn
tz.mbn
hyp.mbn
NON-HLOS.bin
sec.dat
boot.img
recovery.img
system.img.ext4
persist.img.ext4
carrier.img.ext4
persdata.img.ext4
modem.bin
GTESQLTE_USA_SPR.pit
cache.img.ext4
Click to expand...
Click to collapse
///
Is aboot the other file we ned? Which file is the sboot? Also when I try to just flash that combo tar i get:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 786 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I also found these three ROMs none of which work?
{
"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"
}
msaithan said:
I have successfully Unlocked my SM-T377W from Rogers Canada on 7.1.1
I have been Struggling for a while to Unlock the FRP from this device and finally done it
Now its unlocked and I can use whatever sim card i want also
So I have used these 2 files [IT IS IMPORTANT TO USE THE CORRECT COMBINATION AND CORRESPONDING STOCK], maybe you can use the same ones I have used if you do not have a choice
1- Combination "COMBINATION_OYA_FA60_T377WVLU3ARG1"
2- Stock ROM "Firmware SM-T377W T377WVLU3BRG4 [7.1.1]"
So what I have basically done,
1- Turn the device off and put the device in DOWNLOAD MODE
2- Flash the Combination Firmware to your device with Odin
3- When the device restarts and it runs the Combination firmware, turn it off again and put it in "RECOVERY MODE" not download, and in "RECOVERY MODE" do factory reset wipe and click yes then It will restart or maybe shut off
4- Turn it on again normally and it will run the Combination firmware
5- Now Turn it off again and put in "DOWNLOAD MODE" this time
6- From the Stock ROM extract the 3 files (boot, sboot and system) from inside the files of the stock ROM, you will find them inside "AP" and "BL" (cause we have BL, AP, CP, CSC), you need to use 7-zip so you can extract whats inside them
7- Create new file/archive (it will be .tar) using 7-zip with these 3 files (boot, sboot and system)
9- Flash the new file you made .tar (that has the 3 files) in the AP section in Odin.
10- Your done
Step number 7 where I was struggling before, did not know which files to extract and to flash, but after search/attempts finally I figured it out.
Hope this help
Click to expand...
Click to collapse
worked on my uncles sm-t377w that I stupidly told him to factory reset and that stupidly even though done through the settings menu, it decides it wasn't done properly and promptly triggered the FRP and the sim card in the device was no longer active and he is a super genius, so he didn't know what a google account was, what his email address is, what his email password was... poor guy is dying of cancer and just wanted to play games on his tablet but it was giving ANR messages repeatedly. Must remember in the future to remove google accounts before ever factory resetting a tablet, even if done the proper way. So stupid, I could understand if done from the recovery menu, but from the settings menu while logged in and using a screen lock that he at least knew that password for., that should never trigger FRP.
Thanks for helping me help a dying man.
SpectorOfDeath said:
OM*******G --- I GOT THIS TOO WORK FINALLY
just had to take some steps back and think a few things over and try a few things...
I had to alter your instructions abit, but not much, you were bang on for the most part for me....
So what I have done is below, minus the underlined parts, took them out....
---> Good 1- Turn the device off and put the device in DOWNLOAD MODE
---> Good 2- Flash the Combination Firmware to your device with Odin
---> Changed 3- When the device restarts and it runs the Combination firmware, turn it off again and put it in "RECOVERY MODE" not download, and in "RECOVERY MODE" do factory reset wipe and click yes then It will restart or maybe shut off
---> Changed 4- Turn it on again normally and it will run the Combination firmware
---> Good 5- Now Turn it off again and put in "DOWNLOAD MODE" this time
---> ADDED 5.5- RESTART ODIN, not just click restart within Odin, but close and reopen, would not flash the new .tar I make next unless I both skip the factory reset underlinded above && Completely close and reopen Odin
---> Good 6- From the Stock ROM extract the 3 files (boot, sboot and system) from inside the files of the stock ROM, you will find them inside "AP" and "BL" (cause we have BL, AP, CP, CSC), you need to use 7-zip so you can extract whats inside them
---> Good 7- Create new file/archive (it will be .tar) using 7-zip with these 3 files (boot, sboot and system)
---> ADDED 6.5- Make sure Odin has been completed closed and reopened
---> Good 9- Flash the new file you made .tar (that has the 3 files) in the AP section in Odin.
---> Good 10- Your done
Not sure why I had to skip the factory reset as well as restart Odin, I can understand Odin because its a portable version we all use, not system installed, so issues somtimes....
But the factory reset skip was just a tought, that possibly it wouldnt allow me to flash after a factory reset without booting the OS atleast once, and it eneded up being the clintcher for me....
Now there is only one thing I will say about this way to get around FRP, is that you cant preform a factory reset for within the device afterwards, as it re-locks to the old google account again, which means it technically hasnt REMOVED the existing lock, just somehow ignoring the flag. I know this because immediately after I got my .tar to flash and the OS was running and not locked up, I logged into the Play Store and updated play services, and then shut down and I preformed a hard reset within the recovery, just to completely reset the OS one final time and too see what would happen, and it did reformat fine and boot, but was back in its original state, locked to my ex-gfs account, not mine.
SOo I was forced to go thru my steps above again and get back in... worked fine, and I just finshed updateing all my google apps that needed updating in the playstore and seems like everythign is fine, only comes down to not being too factory reset now if I have an issue in the future......
Also brings up my next concern, will I be able to to any future system OTA updates?
I'm not rooted nor do I have any need to be on this device, my LG v30 is rooted already with TWRP, so I havnt broken Knox as far as I know, counter in Download mode is still 0, so Im PRAYING I can do any updates such as those without getting locked out again afterwards....
What I'm hoping, is that over time, what ever 30-90 days, of updates and syncs, that the FRP lock will change to MY google account, not hers, but I have no idea if it will and that only way I can check is to try it in like April, plenty of time and syncing, and see if locks up and I need to do this all over again.
Click to expand...
Click to collapse
I get an error when trying to flash the 3 files. Now I'm stuck with a tablet with Factory Binary on it...Help plz...
onetimepostmaster said:
I get an error when trying to flash the 3 files. Now I'm stuck with a tablet with Factory Binary on it...Help plz...
Click to expand...
Click to collapse
Download same binary version firmware for your device then flash it using z3x 29.5
hi guys trying to do this on grandsons tablet but i get md5 error binary is invalid no mater what combo firmware i use.
ok so i got the combo file to load and flash, after this i got a screen saying factory binary, i waited but would not load past so i did the fatory recovery part and then went to do the next step but now download recover will not work and power button also soes not work . what can i do now.

Categories

Resources