Samsung Galaxy ACE 2 i8160 - SpoofFW "Restore" without any backup [finished]
Hello,
I bought an ACE 2 for my son, he routed these device (without which I knew about...) and does this with a software called heimdall under Linux. He "backuped" his PIT before (which is the partitioning scheme I readed somewhere on xda).
This part is no problem he said (I think differently about this, but...)
Then he wanted to update the firmware, so he downloaded a software called SpoofFW (I found about this app here: http://forum.xda-developers.com/showthread.php?t=959806) and clicked "Restore" under the menu. After that the device tried to reboot and now it is in a thing that is called bootloop I believe (I readed somewhere here on xda about that, the device is booting to the Samsung Logo and then after a while it is booting again and so on)
We have a Linux PC (with heimdall) and I installed on my Windows PC a software called Odin and the Android SDK (have no idea if it is needed, but I readed somewhere that it has a tool named adb which is needed to fix some problems of Android smartphones)
An USB connector and an installed Kies. The phone dosn't responsed to these Software but it dosn't boot up, so I think it is normal. All drivers are get installed which was ask for after pluging in the phone to the Windows PC, except the MPT driver.
Also we have microsd cards here.
The phone comes in the screen for flashing and the screen titled "Android system recovery (3e)", but the last one starts with these output:
-- Appling Multi-CSC...
Can't access to '/system/csc/EPL/system'.
Successfully applied multi-CSC.
Click to expand...
Click to collapse
I can navigat in the menu above with the volum keys.
The problem is I have no idea about android/smartphone rooting things (like my son...), but about computer in general (and I can use the forum search, which delivered no result).
I hope that anyone here can help us with this and do it.
Yours faithfully,
Thorsten Mueller
p.s. he had also written down the product code.
-------------------------------------------------------------------------------
The way to get the Smartphone back to work, after these mistake is to flash the original firmware (for Germany the Poland/2012 April/2.3.6/8160XXLD8/8160OXXLD3 works very well.
Thanks to Messi10 and Der-Knuffi (I clicked on the Thanks button)
boot into recovery mode then wipe data and cache
Messi10 said:
boot into recovery mode then wipe data and cache
Click to expand...
Click to collapse
Thank you for the tip, but that has made no difference. It goes still in bootloop, after a wipe of data and cache.
install stock rom via odin u can ask here for help http://forum.xda-developers.com/showthread.php?t=1700613
Related
OK, my phone is not bricked, but I certainly am…
Trying to reset phone from Chinese to International using posted guide
GT-I9100G
Android 4.0.4
Baseband version I9100GZCLPJ
Kernel version: 3.0.8-1067026
Build number: IMM76D.ZCLPJ
Following the instructions kindly provided by Harchoaoui,
I downloaded the Espresso International i9100g folder and unzipped on my pc.
I then booted my phone to reset (volume up; home button; power button), and wiped “data/factory reset” and “cache partition” (these were the only options available). Removed the battery and connected i9100g with USB cable – Nothing happened!
Tried disconnecting/reconnecting i9100g multiple times – Still Nothing happened!
I repeated this process, following the Guide instructions, several times with the same sad results.
What am I doing wrong?????????????????
I am also seeking clarification of the following:
Assuming that Harchaoui, et al, can set me straight here, I’m still not clear how to manually load Drivers from my PC to the i9100g. More Help needed…
The usb_drv_windows I downloaded contains two sub-folders (amd64 and i386 both containing two drivers [WdfCoInstaller01009.dll and winsubcoinstaller2.dll]. More confusion for this Brick.
…and lastly (I hope): How do I run the omap4430hs_espresso_Inter i9100g.bat file on the phone.
I fully recognize that these are the questions of a complete Brick, but I truly need your help – I’m stuck with a Chinese i9100G that I can’t properly utilize.
PLEASE NOTE: I am posting here because I was not able to post on Q & A Forum
Hey Bro ^^ ...
** First u was able to send me a pm and not post here it's will be faster then this
*** For you to load the the usb driver it's easy just go to device manager then connect your phone you will see a new device connected but no driver intalled on it so left click on it select update driver then select manual update or( let me pick a driver from...) select the main folder usb_drv_windows not amd64 or i386 ...
NOTE you should connect your phone without battery ...
if you need more i can help you with TeamViewer ... just send a pm ^^
I hope that i help u sry if i miss something ...
can't flash back
Hello, i also can't root i9100g , whenever i try to do any official rom it say's that "RE-PARTION FAILED" I don't know why? before i was using cm10 v2.16 then i root to 2.3.6 then my i9100g get updates and i updated it fully the last update was of 10 MB which change my mobile baseband to I9100GZCLPJ and build number IMM76D.ZCLPJ. after getting this update i can't flash or root my mobile. is there any one know how can i fix this problem to root i9100g to any other official rom. i tried, 2.3.6, 4.0.3 and 4.0.4 but every time the same result,
If i connect mt gt-i9100g to pc with usb my phone connects and disconnects immediately and i would not get a chance to install the drivers!!?? I am running windows 10
hi,
After spending many time trying to root my storex tab 901 I bought in france (Already installed on 4.1.1 with google play), Iwas finnaly able to root it using adb and command line.
to do so:
- Download attached file
- Download from google SDK usb_adb_driver
- Go to your device parameters-> USB -> enable debbuging mode
- create a c:\root folder on your windows XP computer then Extract the zip file attached into it.
- Plugin your device to the computer, when prompted for driver, use google sdk USB_ADB_Driver
- When done, open a windows terminal command line
- type: c:
- type: cd \
- type: cd root
- type: cd rootkit
- type: go.cmd
If everything goes well, your tablet should reboot. you can try installing the free app from google store called "Root checker" to confirm your device is properly rooted.
Also, if you lost the original rom and live suite, here is the link to download the latest build from storex web site:
(I will post the link later when I find it)
JB 4.2.2
CAUTION: USE THIS ROM AS YOUR OWN RISK.......Be sure you have the official rom in case it is not working for you. It appears that even though you have the same tablet Reference, depending on when you buy it, hardware might be a bit different and most likely you will take the risk of having a unusable Touch screen or wifi...
I found out you can fully use your Ezee Tab 901 4.2.2
you can install rom from Manta MID 13.
You will be able to install the rom using Livesuite.
Gain:
- Android 4.2.2
- Root Access out of the box
- Play store installed.
Everything will be working
For the link type in google:
MID13 Android 4.2.2 Jelly Bean - Manta Multimedia Info
select google link called: manta.info.pl
select the link catshare or 4shared.
Start live suite 1.7, select the download img file, do a format when prompted. You done.
When the tablet restart, go to the parameter icon, and change language to French or english
Procedure on the Ezee tab 901 with livesuit:
- completly turn off the tablet, unplug cable
- start livesuite and select the downloaded image file
- keep the VOL- button pressed and plug the usb cable
- without releasing the VOL- button press the Power button 6 times.
- You should hear windows sound saying a USB device has been plugged
- if windows request it, install the driver from Livesuitefolder\usbdriver
- Livesuite should automatically start the flashing process.
- when prompted, "Format device" press YEs.
- When it s 100% you tablet should reboot.
Done.
Note: I did not invent anything, thanks to the good work of MANTA team members. I just found out this rom works on my tablet out of the box.
Hi,
Thanks for sharing these tips. I'm gonna try to update to 4.2.2, hoping this is going to fix some problems with this tablet.
I've been looking a lot for information about how to update ezee tab 901, so you did definitely a great work !
edit : iflash went well, but touch screen is not responding anymore. Any idea of how to solve it ?
Thanks.
samus64 said:
Hi,
Thanks for sharing these tips. I'm gonna try to update to 4.2.2, hoping this is going to fix some problems with this tablet.
I've been looking a lot for information about how to update ezee tab 901, so you did definitely a great work !
edit : iflash went well, but touch screen is not responding anymore. Any idea of how to solve it ?
Thanks.
Click to expand...
Click to collapse
Hi,
did you try going into recovery mode and factory reset? (shutdown tabel completely and keep press on volume+key then press power button)
in the menu, using vol+/- scroll down to wipe factory reset and validate by pressing the power key.
Let me know how it goes.
btw, are you sure your tablet is a Ezee tab 901 and not 971?
Cheers
Hi,
Yes I've got 901 and not 971 (written on the back of the device). I tried factory reset , but still the same problem. However, I flashed again with the original rom, and then touch screen went functional again but the wifi switch is kinda "broken" : it's impossible to turn on wifi from the Settings menu.
I returned the tablet where I bought it, seems there's a sort of material problem with it :/
samus64 said:
Hi,
Yes I've got 901 and not 971 (written on the back of the device). I tried factory reset , but still the same problem. However, I flashed again with the original rom, and then touch screen went functional again but the wifi switch is kinda "broken" : it's impossible to turn on wifi from the Settings menu.
I returned the tablet where I bought it, seems there's a sort of material problem with it :/
Click to expand...
Click to collapse
Im sorry to hear that, i dont think something is broken, i had the same issue with a memup tablet, even though it was a same reference, some model had different hardware, sonlike you after testing multiple rom i had only touch s creen and no wifi ( wifi switch went back to off when i tried to turn it on) or on other rom, i had working wifi but no touch screen.
I hope they will replace your device...
Cheers
pierrottls31 said:
Im sorry to hear that, i dont think something is broken, i had the same issue with a memup tablet, even though it was a same reference, some model had different hardware, sonlike you after testing multiple rom i had only touch s creen and no wifi ( wifi switch went back to off when i tried to turn it on) or on other rom, i had working wifi but no touch screen.
I hope they will replace your device...
Cheers
Click to expand...
Click to collapse
Yep the wifi switch is exactly what i've got on this storex. Thanks for your help anyway. Ho and by the way, I properly rooted it with you first tuto
Cheers.
Fast custom ROM 4.2.2 by TOxico for Ezee tab 901
Guys,
I manage to find a very fast and usable rom for our tablet: (THanks to Toxico.) this rom will change your life.
All information and download are in the thread here:
http://forum.xda-developers.com/show...php?p=42274265
It should basically work on any A13 device with livesuit (tested on my Ezee tab 901 and on my 704CET mem up)
This rom comes with no TS driver, but there is all explanation and download to install the needed driver.
note: you might loose the camera though. I encourage you to read the full thread before going further and flash your tablet.
If you want to know the driver used on your tablet, run a adb shell and type lsmod (You will have a list of loaded/used driver.)
Dont be scared, everything is written in the toxico's thread
My only advice, if you dont know how to use adb, do not try it, this is not that easy.
I hope this will help.
Best regards.
As usual do it at your own risk and even more: make sure you have the original rom... just in case
Tutorial for 971.
Hi there,
Does anyone know a tutorial like this one but for the 971??
My brother-in-law wasn't using is so I'm thinking in tweaking it to see how it gets.
MaedaKeiji said:
Hi there,
Does anyone know a tutorial like this one but for the 971??
My brother-in-law wasn't using is so I'm thinking in tweaking it to see how it gets.
Click to expand...
Click to collapse
Hi, sorry i cant help you, it looks like the 971 is using a10 cpu, sôit can be different.
If you know what you are doing, u can try to backup your original firmware and test the solution i have provided from toxico in py post above. But there is no warranty it s going to work.
Any case, donnot forget google is your friend
Good luck
Unfornetly it seems google doens't like this tablet...
I'll see what I can do with some backups and all.
Thanks anyway!
I have been pulling my hair out over my Galaxy S4 recently. I think it is an issue where a virus has embedded itself deep into the OS or flash partitions that are not affected by ROM factory firmware flashing. Everytime I re-flash I have to reformat and wipe cache partition to stop it from being stuck on T-Mobile boot logo. The Samsung boot logo is choppy and not fluid like it once was, indicating extra boot time application loading. I have reflashed different firmwares multiple times and to no avail. I used a VPN proxy called Betternet and now my phone keeps getting internet in different locations of the world following an odd traceroute following the subnet of 10.170.205.XXX before reaching its final destination. And on top of that every new computer I use for mobile hotspot usb tethering it crashes explorer and various other applications on my computer, I'm guessing it is an infected hotspot apk embedded in flash recovery injecting malicious code onto the computer via usb as soon as the usb tether fature is activated. Whenever I put the phone into Kies Recovery mode yellow triangle(where phone will not boot, and no recovery menu with Vol up and power buttons) Kies says it does not recognize the phone and will not let me flash factory recovery firmware. I am pretty sure my phone is irreparable due to so many software issues. Is there any way to get a factory file system Image restored onto the phone. I have tried everything even installing TWRP and removing everything that way, but I have the strangest feeling it doesn't clear some of the flash partitions used for recovery and flashing where this Virus may be hiding it's malicious code and executing it every time I flash factory firmware. I'm on 4.4.4 FNK 16gb Galaxy S4 black model SGH-M919
Any advice I have not mentioned would be greatly appreciated because I do not feel like shelling out another 400 bucks for a new phone.
Thanks for taking the time to read that!
AndroidInitiate said:
I have been pulling my hair out over my Galaxy S4 recently. I think it is an issue where a virus has embedded itself deep into the OS or flash partitions that are not affected by ROM factory firmware flashing. Everytime I re-flash I have to reformat and wipe cache partition to stop it from being stuck on T-Mobile boot logo. The Samsung boot logo is choppy and not fluid like it once was, indicating extra boot time application loading. I have reflashed different firmwares multiple times and to no avail. I used a VPN proxy called Betternet and now my phone keeps getting internet in different locations of the world following an odd traceroute following the subnet of 10.170.205.XXX before reaching its final destination. And on top of that every new computer I use for mobile hotspot usb tethering it crashes explorer and various other applications on my computer, I'm guessing it is an infected hotspot apk embedded in flash recovery injecting malicious code onto the computer via usb as soon as the usb tether fature is activated. Whenever I put the phone into Kies Recovery mode yellow triangle(where phone will not boot, and no recovery menu with Vol up and power buttons) Kies says it does not recognize the phone and will not let me flash factory recovery firmware. I am pretty sure my phone is irreparable due to so many software issues. Is there any way to get a factory file system Image restored onto the phone. I have tried everything even installing TWRP and removing everything that way, but I have the strangest feeling it doesn't clear some of the flash partitions used for recovery and flashing where this Virus may be hiding it's malicious code and executing it every time I flash factory firmware. I'm on 4.4.4 FNK 16gb Galaxy S4 black model SGH-M919
Any advice I have not mentioned would be greatly appreciated because I do not feel like shelling out another 400 bucks for a new phone.
Thanks for taking the time to read that!
Click to expand...
Click to collapse
Could be it's not a virus, but just a lot of apps, or even one rogue app. But, just to be sure, you can do the following. :
1) Download one of these Firmwares to a Windows PC- either one of the top two:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
2) Make sure you have ODIN 3.07 or newer installed on the PC, and that you have the Kies drivers installed. You may have to install Kies to get these.
3) If you have TWRP installed or other recovery, do a full NAND backup to you external SD card
4) Use Advance Wipe in TWRP to wipe Dalvik, System, Data, Cache
5) Use ODIN to flash the firmware you downloaded in step 1. Look here for info:
http://forum.xda-developers.com/gal...odin-thread-return-to-stock-fix-soft-t2915530
This will get you back to full stock. You could make another NAND backup at this point, in case you run into something else.
Don't let the system download/restore any applications. Let it settle in for a few days. If it is working, then allow it to restore your apps.
Hello....I bricked my I927 when I accidently formatted my efs partition when using EFS professional .....my phone boots in download mode.....but only boots till samsung logo screen.....I tried various things like installing stock GB and ICS through odin and installing custom firmware but phone boots onle till samsung logo and then lights up with sone stange colored thin lines and screen goes off.....In TRWP I get a "unable to mount preload" error whenever I try to install somethiing.....I suspect that the EFS partiton is corrupted and needs to be repartioned....I had backupped the efs folder when my phone was working before.....its in a tar format.....I read somwhere that someone made a recovery.zip out of his backedup EFS.IMG and flashed it with CWM solved his problems which were exactly similar to mine.....can somebody on the forum make a recovery.zip for I927 with update binary and script so that I can add the backedup EFS image to it and flash it with CWM? Please.....this would also help many others who are facing similar issues.....and also what do I do regarding the "unable to mount preload" error? I need to repartition and tried to install hemdall.....but get the common .dll error even after following all the instructions and installing C++ 2010.....
Hi, k one thing after the other.
Do you have repartitioned anything?
Do you have adb in place and does adb works when in TWRP?
The easiest thing would be to connect by adb then mount /efs and then restore the efs backup. The good is that you will have a good chance to recover your device. Maybe you need to reformat /efs but that depends.
Which timezone do you live? Maybe a Teamviewer session would be helpful?
.
Thank you for your reply sir...
THANKS FOR THE REPLY SIR....YES I WAS ABLE TO GO INTO CWM RECOVERY AND CONNECT THE PHONE WITH MINIMAL ADB FASTBOOT.....AND AFTER SPENDING ALMOST 2 DAYS CONTINUOUSLY TRYING TO FIND THE PROBLEM USING GOOGLE, I TRIED DIFFERENT COMMANDS ON ADB TO GET EFS BACK OJ THE PHONE....BUT WITH NO SUCCESS...... MY EFS BACKUP IS IN TAR FORMAT......IT WAS MADE USING GALAXYSIMUNLOCK BY SPOCKY.....I LATER TYPED IN 'ADB MESG'.....OR SOMETHING SIMILAR TO THAT COMMAND, AND FOUND OUT THAT ALL THE PARTITIONS ON mmcblk0 were mangled up with strange letters.....for eg, p1, p2, p3 and so on had strange characters written next to them.....SO I TRIED TO RE-PARTITION THE WHOLE THING WITH SDPARTED......AND IT RE-PARTIONED THE SYSTEM (AROUND 7000MB).....MMCBLK01 (AROUND 500MB).....AND ANOTHER THING I CANT REMEMBER NOW.....BUT WHEN IT FINISHED THE JOB, IT GAVE ME A mmcblk02 ERROR.....AND WHEN WHEN I CHECKED MY PHONE ON CWM SCREEN, IT GAVE ME A LIST OF CACHE ERRORS.....AND WHEN I SWITCHED OFF THE PHONE AFTER THAT IT REFUSED TO POWER ON.....IT WAS NOT EVEN GOING INTO DOWNLOAD OR RECOVERY MODE.....BATTERY HAD ENOUGH POWER....SO ITS NOT BATTERY FAULT......I SUPPOSE THAT SINCE THE PARTITIONS WERE FORMATTED THE PHONE BECAME COMPLETELY DEAD......CAN YOU TELL ME IF THERE IS ANY WAY WHERE I COULD GET THE COMPUTER TO RECOGNIZE MY PHONE USING A 'DEAD PHONE USB FLASH' OR SOMETHING.....AND THEN FLASH A BLANK BOOTLOADER AND THEN WRITE CWM?
I LIVE IN INDIA SIR.....+5.30 GMT.....I DO NOT KNOW ANYTHING ABOUT TEAMVIEWER.....IS IT AN ANDROID APP? CAN YOU EXPLAIN MORE IN DETAIL SIR?
PLEASE LET ME KNOW HOW TO GET THE COMPUTER TO RECOGNIZE THE PHONE AGAIN......
Well.. that sounds not that good...
Teamviewer (www.teamviewer.com) is an easy to use and free remote control software for your PC (it runs on both Linux and Windows). We could do a remote control session if you like. I can try to help but cannot promise anything.
I live in Germany: GMT +1. Send me a PM if you want to give that a try. Next Monday. Tuesday or Thursday would be possible on my site. At least for getting a short overview.
.
Thank you sir,
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
alvcross said:
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
Click to expand...
Click to collapse
Ok I have made one. It want to say it was VERY hard to find the correct instructions to do so and therefore I'm absolutely not sure if that will work for you!
Test it if you like but again: I have no idea if that would damage anything more than it is now!
See --> http://forum.xda-developers.com/cap...od-unbrick-debrick-hard-bricked-i927-t3285505
If it worked for you (would be like a miracle) then please report back!
If it does NOT work for you please report back, too!
thanks
xdajog
.
UPDATE:
Besides the link I posted --> Could you please also try the following:
1) Power on your device and directly after that:
2) Press and hold down Vol Up + Vol Down (both the same time)
3) You should see a warning message like the attached one which is the APX mode
4) you need to release the vol buttons immediately after you see the APX mode otherwise it will continue to the non working download mode.
Does teamviewer require internet connection with a lot of data?
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
alvcross said:
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
Click to expand...
Click to collapse
Uhm do you have read my above post??
.
1927 wouldn't boot.....Help.
Ohhhh Thank you.....thank you.....thank you for your kind reply Sir.....how good of you to take all your precious time to help me.....I greatly appreciate all your hard work Sir.....wonderful...*.I wanted to download your img file to try it out and when I read the reply of brother Bubor, that the I927 woudnt boot from the SD card when the bootloader is bricked, I was very disappointed. Like I said before, I have a very very slow internet connection with very less data left....and according to brother bubor's reply I doubt this will work....It looked like he was sure that it wont work....I tried to get into APX mode as the link that brother bubor posted had mentioned, but no luck, as the phone is not going into APX mode.....I remember that when I was trying to get to the APX mode the first time, the computer flashed a notification that the APX driver was not successfully installed.....but after that I tried the method more than a dozen times, but the computer was not recognizing the phone to go into APX mode.....Does the phone go into APX mode when the full internal phone system is formatted? I tried your second method on trying to get to APX mode, but nothing happens.....the computer is not recognizing the phone.....The battery had about 30% power in it when the phone got bricked 2 weeks ago.....Dont know if the battery drained all these days of not using the phone.....And even if I get to the APX mode, I have no idea how to proceed from there to repartition the internal phone system and get back download mode.....In the link that brother bubor posted the person who made the thread has made some files to be used when one gets into APX mode.....The PIT and emmc files which are necessary for repartitioning the system and getting the bootloader work are found in that zip file.....But that zip file is for the I9103 Galaxy R.....there isnt something like that available for the I927 yet.....And is brother bubor sure that the unbrick.img file wont work on the I927?
Give it a try with my unbrick image.
we all don't know.
.
xdajog said:
Give it a try with my unbrick image.
we all don't know.
.
Click to expand...
Click to collapse
Hi @alvcross: any update on this?
have you tried the SD card unbrick?
You said you cannot open the APX mode but what happens when you press the buttons for accessing the APX mode?
Try it even if you see a blank screen and then connect your Cappy with USB to your computer --> you should get a message about a missing driver or similar.
If that works I tell you how to proceed.
xdajog said:
hi @alvcross: Any update on this?
Have you tried the sd card unbrick?
You said you cannot open the apx mode but what happens when you press the buttons for accessing the apx mode?
Try it even if you see a blank screen and then connect your cappy with usb to your computer --> you should get a message about a missing driver or similar.
If that works i tell you how to proceed.
Click to expand...
Click to collapse
im so sorry that i was missing in this thread for a long time now sir.....i have had some issues at home and they have been sorted out lately.....yes sir.....i tried the sd card unbrick image....but my nothing happens.....when i try to hold volume up+power+home buttons and insert usb cable into my computer it says installing drivers and then says drivers failed to install....and nothing happens further.....can you help sir?
alvcross said:
im so sorry that i was missing in this thread for a long time now sir.....i have had some issues at home and they have been sorted out lately.....yes sir.....i tried the sd card unbrick image....but my nothing happens.....when i try to hold volume up+power+home buttons and insert usb cable into my computer it says installing drivers and then says drivers failed to install....and nothing happens further.....can you help sir?
Click to expand...
Click to collapse
Ok so you may try to install the special apx drivers now. Unfortunately I'm on vacation right now so I cannot upload them elsewhere. I come back to you next week.
Sent from my LG-H815 using XDA-Developers mobile app
xdajog said:
Ok so you may try to install the special apx drivers now. Unfortunately I'm on vacation right now so I cannot upload them elsewhere. I come back to you next week.
Sent from my LG-H815 using XDA-Developers mobile app
Click to expand...
Click to collapse
Oh yes Sir....Ill be waiting for the special apx driver package from you....Thank you so very much Sir.....God bless you.....
alvcross said:
Oh yes Sir....Ill be waiting for the special apx driver package from you....Thank you so very much Sir.....God bless you.....
Click to expand...
Click to collapse
No guarantee ! [emoji121]
Sent from my LG-H815 using XDA-Developers mobile app
xdajog said:
No guarantee ! [emoji121]
Sent from my LG-H815 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes Sir....I understand....
alvcross said:
Yes Sir....I understand....
Click to expand...
Click to collapse
Ok could you please try these driver package here: http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875
Follow the instructions there for installing
The next step (if the driver would work for you) will be to flash a working PIT to your device to make sure you are using the correct partitions.
Afterwards we will flash the bootloader (may absolutely brick your device if not done correctly) and then --> if all goes fine --> you should be able to flash in download mode whatever you want to.
So it is still a long way to go and I need to check all the steps first before actually we can proceed.
That may take longer so do not expect that this will be something in the next days.. sorry.
Update:
If the above universal driver do NOT work for you: Test these one here View attachment apx_driver_samsung.zip
.
Thanks for the speedy reply Sir......Ill do as you said and let you know Sir......thank you.....thank you.....thank you Sir....
wooowwww......windows installed the drivers for the phone and it shows up as "NVIDIA usb boot-recovery for mobile devices." But when I open minimal adb and fastboot and type 'adb devices' the phone doesn't show up in the 'list of devices attached'....the line after 'list of devices attached' is just empty.....Also the phone doesnt show up in odin....what should I do next Sir?
alvcross said:
wooowwww......windows installed the drivers for the phone and it shows up as "NVIDIA usb boot-recovery for mobile devices." But when I open minimal adb and fastboot and type 'adb devices' the phone doesn't show up in the 'list of devices attached'....the line after 'list of devices attached' is just empty.....Also the phone doesnt show up in odin....what should I do next Sir?
Click to expand...
Click to collapse
nvidia apx isnt fastboot/adb device. You can found tool on nvidia site ( more info https://ac100.grandou.net/nvflash ), this tool can read and write whole flash.
Before you could use nvidia's tool, you must send an uniq blob to your phone. APX mode is useless without this blob.
This blob is uniq for every phone.
Samsung Galaxy Tab S4 in bootloop.
Hey there.
I have a tablet - Samsung Galaxy Tab S4. There was quite a lot of data on it, but it worked fine. Recently, it turned off without any reason and after that it could no longer turn on. Now the tablet has an eternal reboot and it does not boot into the system.
Error in recovery:
! ! Caution! !
Not enough storage resource.
Perform "lacking storage booting".
The recovery says that I can try to boot my tablet using lacking storage booting. But for some reason, I don’t see such an item in the recovery (please look at the photo: https://postimg.cc/XBFrycqF/c9784539). Maybe I should try to install different version of official Samsung firmware or different version of official Samsung recovery that will have function of lacking storage booting?
I understand that this issue is because my tablet hasn't enough memory and something needs to be removed from memory to allow the tablet to boot.
I know that there is variant to delete all data from the tablet - use factory reset through recovery, but I cannot do this because there is important data stored on the tablet.
Please help me what can I do in this situation and how can I enter to the file system for delete something from the tablet? Maybe can I delete some unnecessary files by connecting the tablet to a computer? When I tried to connect the tablet to the computer, nothing happened - the computer does not see the tablet.
I have tried to boot in safe mode but it not helped me
Also I had an idea - install custom recovery TWRP, but as I understand - Samsung Security Folder will be deleted after that due to Knox protection triggering. It also no good for me because I store my important data in Samsung Security Folder. I have tried severely times wipe cache partition, but it's not working for me.
Help me please.
Thanks a lot.
By the way, I found information on the Internet about programs: system recovery program - ReiBoot-Android System Repair from Tenorshare and data recovery program - Tenorshare - UltData for Android.
Has anyone heard of these programs?
Maybe they will help in my case?
I thought about solving this problem and it seems to me that first of all it is worth paying attention to the following:
Samsung recommends to use the lacking storage booting mode in recovery - maybe it's worth to try to use it?
But the problem is that I could not find such a function in my recovery. Maybe it's hidden somewhere?
I think that probably there is no such function in my recovery. If it's true, it's might be worth to try to install different version of the official recovery by Samsung, which will have a boot function - "lacking storage booting".
In result the Knox counter will not work and all data will not have to be deleted from the tablet.