Hey everyone,
Please to be here and ever since I changed from Iphone to an Android, I am reading, flashing and trying new things with my device.
Unfortunately, I already came accross the biggest problem which you can have and I have no Idea what to do, nor do I find anything about this topic in the internet.
My Problem:
I flashed a developer version of the new Lollipop OS on the Phone, which did not really work... So I wanted to go back to KitKat 4.4.4 but also this didnt work and I tried a lot but as this developer version was very unstable, I couldnt install a custom recovery so I was stuck.
After a while I was so frustrated so I did the following:
First: I followed the instructions like in this FAQ to install the Kitkat version, which worked fine ainotech.com / how - to - flash - lenovo-s90 -sisley-root- and-custom-firmware (I added some spaces as i am a new user in here)
2. After I was so frustrated, I went into the bootloader mode, so I got access to the Com-ports
3. There I applied the bootloader unlock "trick" using QFIL and I hit the download button, after that the phone switched off and now is only vibrating shortly every 5 sec quickly.
I can plug it on the USB or on the charger, I can press buttons long or what so ever, but it does not switch on nor does it get recognised by the PC... NOTHING!
So any suggestions what I could do?
Thanks
did u try turn on your phone with volume up key pressed together with power button and go into recovery mode?
if u can enter recovery mode then u can flash any firmware using qfil from there.
lawong said:
did u try turn on your phone with volume up key pressed together with power button and go into recovery mode?
if u can enter recovery mode then u can flash any firmware using qfil from there.
Click to expand...
Click to collapse
Dear lawong,
Yes I tried everything like that but I think I hard pricked it.
Worst part for me is, that even after uninstalling all USB drivers, the phone still did not get connected nor detected by the computer.
have u already tried to charge your phone like 5hours+++ and then try once again plug in to your laptop ?
im bricked my s90 before when upgrading to lollipop and then downgrading back to kit kat , but manage to unbricked it with flashing full kitkat firmware using qfil.
well . i manage to super hard bricked my s90 with flashing s90t firmware to my s90a ,at fisrt its stuck in lenovo logo ,no recovery ,then after playing with emmc software download its completely dead. black screen with long vibrate. after a lot of trying. only one tools that really revive back my s90 to its fully fnctional. its called "miflash"
Can you send the thread how to fixed by miflsh tool
Sent from my Blade S6 using XDA Free mobile app
---------- Post added at 12:14 PM ---------- Previous post was at 12:09 PM ----------
Hey everyone,
Please to be here and ever since I changed from Iphone to an Android, I am reading, flashing and trying new things with my device.
Unfortunately, I already came accross the biggest problem which you can have and I have no Idea what to do, nor do I find anything about this topic in the internet.
My Problem:
I flashed a developer version of the new Lollipop OS on the Phone, which did not really work... So I wanted to go back to KitKat 4.4.4 but also this didnt work and I tried a lot but as this developer version was very unstable, I couldnt install a custom recovery so I was stuck.
After a while I was so frustrated so I did the following:
First: I followed the instructions like in this FAQ to install the Kitkat version, which worked fine ainotech.com / how - to - flash - lenovo-s90 -sisley-root- and-custom-firmware (I added some spaces as i am a new user in here)
2. After I was so frustrated, I went into the bootloader mode, so I got access to the Com-ports
3. There I applied the bootloader unlock "trick" using QFIL and I hit the download button, after that the phone switched off and now is only vibrating shortly every 5 sec quickly.
I can plug it on the USB or on the charger, I can press buttons long or what so ever, but it does not switch on nor does it get recognised by the PC... NOTHING!
So any suggestions what I could do?
Thanks
I have the same problem.
werwird said:
Hey everyone,
Please to be here and ever since I changed from Iphone to an Android, I am reading, flashing and trying new things with my device.
Unfortunately, I already came accross the biggest problem which you can have and I have no Idea what to do, nor do I find anything about this topic in the internet.
My Problem:
I flashed a developer version of the new Lollipop OS on the Phone, which did not really work... So I wanted to go back to KitKat 4.4.4 but also this didnt work and I tried a lot but as this developer version was very unstable, I couldnt install a custom recovery so I was stuck.
After a while I was so frustrated so I did the following:
First: I followed the instructions like in this FAQ to install the Kitkat version, which worked fine ainotech.com / how - to - flash - lenovo-s90 -sisley-root- and-custom-firmware (I added some spaces as i am a new user in here)
2. After I was so frustrated, I went into the bootloader mode, so I got access to the Com-ports
3. There I applied the bootloader unlock "trick" using QFIL and I hit the download button, after that the phone switched off and now is only vibrating shortly every 5 sec quickly.
I can plug it on the USB or on the charger, I can press buttons long or what so ever, but it does not switch on nor does it get recognised by the PC... NOTHING!
So any suggestions what I could do?
Thanks
Click to expand...
Click to collapse
Hi,
I have the same problem.
I have a lollipop 5.0.2 rom. but I flash the wrong unlock_bootloader(kitkat bootloader)
Now my phone hard bricked and dead.
Did you find the solution?
Thank you.
Hi,
I solved the problem.
How;
Firstly disassembly lenovo s90. ( https://www.youtube.com/watch?v=8SW_DlAlwEk )
Remove the battery socket.
Connect USB after power button 1 second.
Computer see Qualcomm QDLoader HS-USB port ( 9008 ).
and after QPST - QFIL with Flash rom Lenovo Sisley (S90-S90 U-T) - Offical QPST-firmware VIBEUI_V2.0_1512_ST5.HH.1
and happy ending.
Please help
Hello everyone!
I have the same problem as lawong with my S90U(2Gb). Phone after switching has a long vibration, then switches to 9006.
Was flashed it using MiFlash and QFIL in the instructions (the phone disassembled) - in the end two results:
1) logo for a long period of vibration, 9006 with many disks;
2) the logo, cyclic restart.
A few times the phone was even launched, the firmware was working correctly, IMEI is not lost. But after shutting down or restarting all over again.
I think it's not hardware. Otherwise most likely would have been problems in the flashing process and I think I wouldn't be able to run it a few times.
I have the feeling that something goes wrong while loading.
lawong, what firmware you have restored your phone using MiFlash?
In the firmware that I found for QFIL missing files .bat and there are a lot of images .img - As in the screenshot.
{
"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"
}
Please advise how to be?
vanomc said:
Hello everyone!
I have the same problem as lawong with my S90U(2Gb). Phone after switching has a long vibration, then switches to 9006.
Was flashed it using MiFlash and QFIL in the instructions (the phone disassembled) - in the end two results:
1) logo for a long period of vibration, 9006 with many disks;
2) the logo, cyclic restart.
A few times the phone was even launched, the firmware was working correctly, IMEI is not lost. But after shutting down or restarting all over again.
I think it's not hardware. Otherwise most likely would have been problems in the flashing process and I think I wouldn't be able to run it a few times.
I have the feeling that something goes wrong while loading.
lawong, what firmware you have restored your phone using MiFlash?
In the firmware that I found for QFIL missing files .bat and there are a lot of images .img - As in the screenshot.
Please advise how to be?
Click to expand...
Click to collapse
no need to tear down your phone bro , im fixing mine before without tear it down , but im sorry i forgot the procedure as im no longer using s90 , but for sure it willbe fixed using miflash . if failed try it again n again .
Related
Hi
After i rooted my phone using Odin , my phone started rebooting but stuck at sasung logo screen forever . I tired factory hard reset nothing works .
I heard Odin can put me back into original factory reset? But i need the XDA file? Help please i'm new
dxy2jbaby said:
Hi
After i rooted my phone using Odin , my phone started rebooting but stuck at sasung logo screen forever . I tired factory hard reset nothing works .
I heard Odin can put me back into original factory reset? But i need the XDA file? Help please i'm new
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1740367
Do some reading up on your issues, do a search, kk and don't be this cat...
{
"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"
}
bigjoe2675 said:
http://forum.xda-developers.com/showthread.php?t=1740367
Click to expand...
Click to collapse
This thread has so much information , is there a direct solution?
dxy2jbaby said:
This thread has so much information , is there a direct solution?
Click to expand...
Click to collapse
THIS WILL FIX YOUR ISSUE AS I WENT THROUGH THE SAME PROBLEM YOU ARE EXPERIENCING.
WARNING IT WILL DELETE YOUR DATA. IF YOUR DATA IS IMPORTANT FIND ANOTHER MEANS...
You MUST have Kies full installed on the desktop/laptop and make sure you're updated to the latest version.
1) Boot your note into download mode(hold down volume button at the same time as the power button, let go of power button when you feel
your phone vibrate but keep holding down button until you see a prompt to push up volume button to continue or down volume button to
cancel, hit the up button your are now in download mode.)
2) Connect your Note to the laptop with factory USB cable
2) Launch Kies on your desktop (full version)
4) Choose Tools, Firmware upgrade & initialization
a) While in download mode, pull battery and enter the S/N & model name (ALL CAPS!!)
b) It will prompt to initialize to original settings. Click "YES"
c) It will prompt to initialize the latest version. Click "YES"
d) It will download the firmware upgrade components (DO NOT DISCONNECT THE DEVICE!!)
5) It will prompt for firmware upgrade and initialization.
a) Click check box for reading above information
b) Click your choice if you want your information saved on Samsung Kies corporate servers (I choose WITHOUT saving).
Just kick back, wait and the phone will update to the original out of box software with the latest updates already applied. No issue with anything, no tripping of the flash counter, and Samsung/AT&T knows now different (if you tripped the counter back before performing this, or performed the process of installing CWM recovery through ADB as to NOT trip the flash counter when changing recovery).
This is the EXACT process I did, and had an AT&T tech verify and it's not detectable I was rooted, and was running a custom ICS ROM. Now, I will qualify that I DID the Recovery installation with ADB so that I didn't trip the counter with the Recovery installation. So if they are able to check the binary information to detect modification even with flash counter reset, that's out of my hands and can't confirm or deny.
You may have to do this process multiple times for it to work.
It worked 1st time for me but another guy had to do it 10 times!
THIS WILL FIX YOUR ISSUE AS I WENT THROUGH THE SAME PROBLEM YOU ARE EXPERIENCING.
WARNING IT WILL DELETE YOUR DATA. IF YOUR DATA IS IMPORTANT FIND ANOTHER MEANS...
isimme said:
THIS WILL FIX YOUR ISSUE AS I WENT THROUGH THE SAME PROBLEM YOU ARE EXPERIENCING.
WARNING IT WILL DELETE YOUR DATA. IF YOUR DATA IS IMPORTANT FIND ANOTHER MEANS...
You MUST have Kies full installed on the desktop/laptop and make sure you're updated to the latest version.
1) Boot your note into download mode(hold down volume button at the same time as the power button, let go of power button when you feel
your phone vibrate but keep holding down button until you see a prompt to push up volume button to continue or down volume button to
cancel, hit the up button your are now in download mode.)
2) Connect your Note to the laptop with factory USB cable
2) Launch Kies on your desktop (full version)
4) Choose Tools, Firmware upgrade & initialization
a) While in download mode, pull battery and enter the S/N & model name (ALL CAPS!!)
b) It will prompt to initialize to original settings. Click "YES"
c) It will prompt to initialize the latest version. Click "YES"
d) It will download the firmware upgrade components (DO NOT DISCONNECT THE DEVICE!!)
Thank for the solution , but does it mean i cannot root my phone? will it stuck at the sasumg logo screen again if i use odin to root it?
5) It will prompt for firmware upgrade and initialization.
a) Click check box for reading above information
b) Click your choice if you want your information saved on Samsung Kies corporate servers (I choose WITHOUT saving).
Just kick back, wait and the phone will update to the original out of box software with the latest updates already applied. No issue with anything, no tripping of the flash counter, and Samsung/AT&T knows now different (if you tripped the counter back before performing this, or performed the process of installing CWM recovery through ADB as to NOT trip the flash counter when changing recovery).
This is the EXACT process I did, and had an AT&T tech verify and it's not detectable I was rooted, and was running a custom ICS ROM. Now, I will qualify that I DID the Recovery installation with ADB so that I didn't trip the counter with the Recovery installation. So if they are able to check the binary information to detect modification even with flash counter reset, that's out of my hands and can't confirm or deny.
You may have to do this process multiple times for it to work.
It worked 1st time for me but another guy had to do it 10 times!
THIS WILL FIX YOUR ISSUE AS I WENT THROUGH THE SAME PROBLEM YOU ARE EXPERIENCING.
WARNING IT WILL DELETE YOUR DATA. IF YOUR DATA IS IMPORTANT FIND ANOTHER MEANS...
Click to expand...
Click to collapse
Does this mean if i root my phone using odin again same problem will occurs?
dxy2jbaby said:
Does this mean if i root my phone using odin again same problem will occurs?
Click to expand...
Click to collapse
Yes more then likely. I had the same problem when rooting, I used the fix I provided then tried rooting and got the same issue.
So I fixed again and then used another rooting method. Sorry but I cannot remember what rooting methods I used. You gotta
do some homework and find another root method. Put in the time it will pay off! Good Luck
You don't root with Odin. You flash cwm with Odin then flash super user with cwm to gain root. Or just flash a ROM with cwm and you'll be rooted.
You don't need kies at all.
Download the proper Odin stock package for your phone. Then put your phone in download mode, flash that with Odin. Once that finishes you'll be stock and no root. Find the Odin flashable cwm package. Flash that with your phone in download mode. Then put a ROM on your internal storage, reboot into cwm, and flash the ROM. You'll have a better experience than stock, and it will be rooted.
And don't worry about the flash counter. No reason to. People have gotten warranty exchanges no problem with their counter tripped. As of right now neither ATT nor Samsung care that it's tried so long as you go back to stock before you exchange.
And please, read a bunch. As much as you can. It's not hard to learn the process I just described. And it will Dave you from future issues like you're experiencing.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
bigjoe2675 said:
http://forum.xda-developers.com/showthread.php?t=1740367
Click to expand...
Click to collapse
Do some reading up on your issues. . .
Hey buddy,
Just use the link Bigjoe sent you. Follow the steps 1-2-3.
Thank i finally got it , i just installed the new ROM
http://forum.xda-developers.com/showthread.php?t=1669170 S3 ROM
I want to delete atnt stock apps also where do i go to download apps? I know for iphone i use installous
One last newbie question how do i restore apps from SD card to my phone
Hey a little help here. I have this issue right now after trying to root. I am following the directions on this post to go back to the official firmware but i'm having a problem locating the S/N. This is a replacement phone i got out of warranty last week. I was able to root/unroot my old phone but that was still in GB b/c I didn't update it due to the bugs in ICS. Well this one already had ICS and now I'm having a ****load of problems.
The only numbers I see on the phone behind battery is the
IMEI
SKU
FCC ID
Where do I find the S/N to put into keis?
Your SN
PiercedWithAttitude said:
Hey a little help here. I have this issue right now after trying to root. I am following the directions on this post to go back to the official firmware but i'm having a problem locating the S/N. This is a replacement phone i got out of warranty last week. I was able to root/unroot my old phone but that was still in GB b/c I didn't update it due to the bugs in ICS. Well this one already had ICS and now I'm having a ****load of problems.
The only numbers I see on the phone behind battery is the
IMEI
SKU
FCC ID
Where do I find the S/N to put into keis?
Click to expand...
Click to collapse
If you go into your settings, about phone, and click status, you should see your sn 2nd item from the bottom
Connecting endlessly
Little help please with the Kies recovery method:
it connects endlessly for me. I can still do the Firmware upgrade through the menu, but then it will ask for a model number and no matter what I put there it won't accept it...
The model number is SGH-I717 If I remember correctly all caps, you probably already tried that thou.
Have you tried using Oden?
Sent from my SAMSUNG-SGH-I717 using xda premium
The number part is i717
india seven one seven
problems with flashing
Hello.My phone died mysteriously one night and won't boot into normal android system as it used to. I tried to do firmware emergency recovery in kies, but it remains stuck at 3%. I also tried do flash stock rom through odin, but it always stuck at system.img.ext4. Any help is greatly appreciated.
Q&A for [GUIDE] Fix an unflashable or soft bricked I9100G
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE] Fix an unflashable or soft bricked I9100G. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Samsung Galaxy S2 i9100G
i TRIEED THE ABOVE METHOD BUT WAS NOT ABLE TO UNBRICK MY PHONE. I HAVE A ROOTED PHONE WITH 4.1.2 . I TRIED INSTALLING CMW RECOVERY BUT FLASHED FILE OF "GT-I9100" AND BRICKED MY PHONE.
FISTLY IT WAS GOING INTO DOWNLOAD MODE I TRIED INSTALLING STOCK ROM WITH ODIN BUT ODIN "FAIL" ERROR SHOW THEN AFTER MY PHONE IS STUCK ON "PHONE >>>>YELLOW MARK>>> COMPUTER" LOGO.
pLZ HELP ME HOW TO GET BACK AND UNBRICK IT.
THANKS
Phistachio said:
Hello everybody
Due to some demand and request, I've decided to adapt my guide to the I9100G. It deserves some love too!
This is a guide dedicated to noobs, so if you're not one, I would advise to stop reading now! (altough feedback would be great! )
Yes, there have been quite a few threads about fixing a soft brick. But what I'm writting now is another solution to a different kind of problem : unflashable GSII (which also works with a soft brick of course ), which is a soft brick and a corrupted NAND rw (read/write) function.
Just in case you don't know, a soft brick occurs when you flash a ROM or Kernel, and it doesn't go your way, thus bricking the "soft part", aka Software, of your phone. Therefore, it is easy to recover from. Now, regarding NAND rw (NAND's read and write function being the corruption) it means that it is an issue deeper than a soft brick.
It is obvious when you can flash a kernel, but you can't flash a ROM, because it can't properly read the NAND, but can flash a kernel. But you ask, why the kernel? Because flashing a kernel is a bit deeper than flashing a ROM. When you flash a kernel, you're changing/putting new instructions to the hardware, and when flashing a ROM, the instructions that are drewn are different and more "simple", so when flashing, ODIN will say "FAIL" instead of "PASS", or suddenly stopping the flash out of nowhere.
BUT UNFORTUNATELY, this guide will not be able to fix a NAND r/w corruption, due to tyhe fact that I do not have either the .PIT, the bootloader or the kernel, I only have a stock ROM, which will only fix a soft brick.
As soon as I get my laptop back from RMA (this Pentium Dual core I'm using right now isn't trustworthy), I'll extract the zImage and sbl.bin from each ROM, zip it, upload it, and add the rest of the guide.
UPDATE 02/05/2012
GOOD NEWS EVERYONE!Thanks to maui75, I have the .PIT and the gingerbread bootloader! When my laptop arrives from RMA, I'll download and unzip all the packages in this thread, add the .PIT, zip, upload again, and add the rest of the guide! __________________________________________________
________________________________________________
IMPORTANT ANNOUNCEMENT #2
Please welcome neerajganga, your new thread maintainer (along with me)! He has been of great help, so I think he deserves this kind of announcement![/center]
________________________________________________
IF YOU ONLY HAVE A BOOTLOOP
Wipe data/factory reset and wipe cache. IF THAT DOESN'T WORK, MOVE ON WITH THE GUIDE
__________________________________________________
Let's start with the basic files, downloads and requirements
1) You have to know the basics of ODIN and flashing (duh )
2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers
3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II
4) Download the necessary ROM (they are Gingerbread 2.3.6) : Africa (Iraq), Asia (Malaysia), Europe (Open Austria), Middle East (Saudi Arabia). (password is samfirmware.com)
5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano
And that is it! Let's get down to business
__________________________________________________
If your GSII has the folowing symptoms :
Bootloop
Stuck on GSII logo, but already removed the battery to try to fix it
Enters Download mode and Recovery mode
It means that you are soft bricked and is easy to solve.
But if your symptoms are the mentioned above, PLUS the symptoms below
Enters Download mode but does NOT enter recovery mode (usually means a NAND rw corruption)
Doesn't flash
Bad flash in odin (FAIL after flashing, or the flashing suddenly stops)
Then it means that you have a bigger issue, such as the aforementioned NAND rw corruption.
It's time to open up ODIN and start reviving your phone!
__________________________________________________
First of all, let's just have a quick glance of how ODIN looks like, and where we should put the files :
{
"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"
}
As the picture clearly shows, the green rectangle is where you can tick. Those 2 which are ticked must remain that way. And the red one is well... Where you SHOULDN'T touch
But where are the files going, you say?
.tar -> PDA
__________________________________________________
Recovering a soft bricked phone
1) Grab the Recovery Package, and put the file in its place.
2) Turn off your phone. Enter Download mode by presing Vol. Up + Home + Power button.
3) Plug in your phone. It will show you, in a yellow box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9, or other numbers)
4) Once ready and done all your prayers, press Start. Wait patiently. It usually takes 5 minutes to flash.
Have you done everything correctly until now? Then...
Congratulations on recovering your phone!
You deserve some cake afterwards, and some rest
I hope that this guide was helpful, and if it was, hit the thanks button!
Credits mainly go to Intratech and Sammobile, for his amazing gallery of ROMS and files
_______________________
Disclaimer
This is to be used as educational information. I am not liable of any damage that may occur to your phone.
Click to expand...
Click to collapse
pls give me your contact detail...i have same problem.
Galaxy S2 which was stuck in "Phone-Exclamation-Computer" icon mode. Couldnt even get into Recovery or Download mode.
My phone showed up on Odin so i just flashed it with the stock firmware. ....tell me how to flash with the stock firm ware
?
hello
please update the download link i cant download the galaxy s2 gt-i9100 recovery package rom ...
I9100G soft brick - don't want to charge
Hello guys,
I think I made a mistake today, I was trying to install a 4.4 ROM from OMNI on my S2 I9100G, but have to flash a recovery first with ODIN (i was coming from stock JB). I have installed a CWM version with ODIN, but the device don't want to enter in recovery, then tried another time to install CWM recovery, but accidentally flashed a wrong one, from I9100 not I9100g version.
How my phone is stucked on first logo when I power up, and don't want to charge, even if it's off (the animation does not fill up the battery icon, it's only a loop, the battery icon just appear and dissapear), the device is not charging. Also, now my computer don't see it anymore, neither ODIN.
What I have to do?
Hey!
Anybody here? I really heed some help.
alinduplea said:
Anybody here? I really heed some help.
Click to expand...
Click to collapse
This is what happens when you brick your device. I guess your PC can't detect your phone even in download mode too right? Next time (if there's even one), make sure you 100% understand that you are flashing the rom/kernel for the correct device. There is nothing else you can do to your phone.
Not detected even in download mode
gsstudios said:
This is what happens when you brick your device. I guess your PC can't detect your phone even in download mode too right? Next time (if there's even one), make sure you 100% understand that you are flashing the rom/kernel for the correct device. There is nothing else you can do to your phone.
Click to expand...
Click to collapse
But phone still power up... It can't be dead, there must be a solution to fix it.
can't download the ROM
Please developers, anybody can give me a working link to download the ROM ?
thank you
how to revert S2 (i1900g)?
mostly the rom link is dead..
s2 9100g stuck at boot screen -displaying SAMSUNG GALAXY SII I9100G
The phone was working perfectly fine and it suddenly restarts and my phone is now displaying SAMSUNG GALAXY SII I9100G .Not able to enter recovery mode or download mode, odin does not recognize it. I guess odin recognises the phone only after you put the phone on download mode.When i try to put the phone on recovery or download mode the sceen goes blank?Is my phone recoverable?Is it soft brick or hard bricked. Please help.
Is there any way i can revive the phone back.I have some important data on it.
Hello friends.
Need couple advices.
Just became an owner of this phone.
No ROMs available, nothing yet, phone is new, I understand.
But,
1) I can`t enter neither recovery nor fastboot ("no command" with fallen robot with red warning in stomach instead of recovery and some factory mode instead of fastboot).
2) Drivers.. what`s with them? Any advice? (adb at least, PC doesn`t see the phone, except file transfer)
3) twrp?) root?) xposed?))) (android 7.0)
Will be very grateful for any help
Great questions. I have also ordered the phone but have not yet received it.
Would you like to tell us a bit about the phone? Does it work well? Do the stereo speakers work or is one speaker just a fake?
-Tiz- said:
Great questions. I have also ordered the phone but have not yet received it.
Would you like to tell us a bit about the phone? Does it work well? Do the stereo speakers work or is one speaker just a fake?
Click to expand...
Click to collapse
Thanks)
Works fine, a bit heavier than i expected, but now i like it.
stereo is fake, as usual
Already managed to enter recovery, fastboot, to connect from pc in fastboot. But still fail with adb drivers.
Found scatter file, that should suit, and now going to try readback firmware from the phone.
Then want to experiment with different TWRPs, and so on
On 4pda, they tellin about androidpay problems
My cam is ok, but one`s guy from 4pda - just terrible, may be he need to factory reset.. we`ll see
that`s it for now
I have this on order from Amazon. I'm really hoping someone with the skills will be able to get TWRP and Lineage setup for the S60. I'm a noob at this, especially about MTK devices. How hard would it be to port over a build from an existing phone with the same general config (Helios P25, 6 + 64 GB)? I have concerns after reading about finding malware on the X5 Pro and I'd like to mitigate that.
Those of you that already have your S60's, are you aware of any pre-installed adware or other unwanted software? Seems to be a very common issue on Doogee handsets....
What is the real weight of the Doogee S60 handset please? Various spec sites and retailers have it listed from 173g to 337g! They can't all be right. Doogee don't list the weight on their website so I expect it to be bit heavy. I will be really grateful if someone who has one can put it on a scale and weigh it.
I've just received mine.
It's 289grams
The truth at last
fingery said:
I've just received mine.
It's 289grams
Click to expand...
Click to collapse
Thank you a lot.
At last some genuine information!
Doogee never answered my emails and don't list the weight in their specs. I did get a reply from one retailer who said it is 202g and they get their specs direct from Doogee so it must be correct. I was suspicious so thought I would ask here where there is no commercial pressure to deceive.
It is a bit hefty at 289g so will now look for another rugged phone - any recommendations?
Just received today.
297 gr as you can see in attached pic.
I am also interested on rooting, TWRP... and also very interested on Bluetooth+ plus ANT+ service. I don't know if this o is possible in this phone, but very interested to me for connect with heart rate monitor ANT+ (this works very well with my previous Nexus 5).
Any information will be appreciated!
Thanks.
Ruben
PD: Sorry, pic is on Google photos and I can't attach it or putting a link to it!
Curiousdrummer said:
Thank you a lot.
At last some genuine information!
Doogee never answered my emails and don't list the weight in their specs. I did get a reply from one retailer who said it is 202g and they get their specs direct from Doogee so it must be correct. I was suspicious so thought I would ask here where there is no commercial pressure to deceive.
It is a bit hefty at 289g so will now look for another rugged phone - any recommendations?
Click to expand...
Click to collapse
{
"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"
}
Having spent a few hours setting up my S60 yesterday i have a few issues. Can anyone clarify if this is just me or are we all seeing similar :
Fingerprint reader - easy to setup and seems to detect quickly however once configured it's very poor in use. More often than not the device fails to recognise my print and unlock.
NFC - Annoying notification "NFC service. Touch to view settings" cannot be hidden/removed.
NFC - Android pay not working. Error message saying device may be unlocked or rooted etc.
Build details etc shown on attachment.
I heard somewhere that S60 is prerooted, maybe thats issue with Android Pay?
Chamelleon said:
I heard somewhere that S60 is prerooted, maybe thats issue with Android Pay?
Click to expand...
Click to collapse
Shame they market it with NFC and using it to Tap and Pay but Android Pay isn't supported on it.
Any idea if there's any way around before i spend hours on it?
fingery said:
Shame they market it with NFC and using it to Tap and Pay but Android Pay isn't supported on it.
Any idea if there's any way around before i spend hours on it?
Click to expand...
Click to collapse
I have set upa third part application to pay, and it seems to work, but I haven't used yet. I also have read the warning with Android pay, but in spain there are other apps supported by banks. But yes, it is annoying the nfc notification always on task bar.
And my fingerprint sensor is working correctly.
Ruben
Enviado desde mi Nexus 7 mediante Tapatalk
I find it hard to believe they pre-root the phone from the factory although kudos if they did. For those of you with your phones already have you installed any anti-malware and what has been the result? I've been reading up on the issues the X5 Max Pro owners have been having and I'm hoping to avoid that s***storm if I can.
fingery said:
Shame they market it with NFC and using it to Tap and Pay but Android Pay isn't supported on it.
Any idea if there's any way around before i spend hours on it?
Click to expand...
Click to collapse
on many Chinese phones, Android Pay does not work because google servers do not certify!
their certification on a certain phone requires financial costs.
But Android Pay is easy to run having root rights
TWRP and ROOT access will be ready soon!
STOCK ROM + TWRP + ROOT + XPOSED (is said to be buggy)
First of all i should thank a lot and redirect all regards to this very man serg2327, because all that below is totally his merit
Firstly, speaking about drivers, I didn`t install any extra, just the ones the phone did automatically. You only need to connect ur phone to ur pc in different states (e.g. turned off, recovery, fastboot) and all will be installed by itself (except adb drivers)
STOCK ROM
Was made from full (64gb) memory dump.
I cant post links, i`m very sorry
U can google them at the theme of doogee s60 at 4pda.
Or, may be serg2327 will post them here
1. Unpack the firmware
2. In SP Flash Tool point to the scatter file containing in firmware
3. Flash any partition u want (I flashed all of them and everything was fine)
TWRP + ROOT *(+XPOSED)
twrp is ported from BV8000
there`s a touchscreen bug, but there`s also some temporal solution
supersu is also taken from BV8000
Recovery could also be flashed thru SP Flash Tool, u just need to tick it in download menu and put the right path, but in this case, due to a touchscreen bug u will need an otg cable and a mouse, otherwise u won`t be able to flash supersu and that will cause in loosing twrp after booting system.
That`s why we will flash recovery thru fastboot, because there during the first boot - touch is available, but only for the first time, afterwards it will also fail.
So,
1. Download and place recovery.img somewhere, copy the path. I place it just in C:\ for convenience.
2. Download and place supersu.zip into the /sdcard of your phone (do it while your phone is on, before proceeding further, because in twrp my pc couldn`t see the phone)
3. Turn off the device, then press and hold together "pwr" and "vol+" until the screen turns on, then u see a green robot with a red warning in the stomach, then press and hold "pwr" and then just slightly press "vol+" (don`t hold it, and press only after "pwr" is held), u`ll see the stock recovery menu, choose with "vol-" fastboot mode (or bootloader, don`t remember, it is second from upwards), press "pwr" to enter this mode, u should then see just a small FASBOOT written on a black screen.
4. Connect the phone to the pc, open cmd.exe as an Administrator, type:
fastboot devices
u should see ur phone by its serial (like adb devices)
if everything is ok, go next.
type in cmd:
cd C:\ (or other path where the recovery is lying)
fastboot flash recovery recovery.img
fastboot boot recovery.img
then u`ll get ur phone booting in twrp, and touch should work this time
5. Flash supersu from /sdacrd
*5.1. If u like, can also flash xposed (it is beta version, is said to be buggy) at this very moment, while u have ur touch available
6. Wipe dalvik cache and boot to system
*7. For using xposed u need an installer (ticking modules, etc)
8. Open supersu, it will ask for a binary update, press cancel and forget about it.
9. That`s it, u have twrp + root.:good:
p.s. The firmware is deodexed, that means we can freely clean chinese system trash.
And, one more great thanks and regards to serg2327 . It`s more of his knowledge than mine
link to firmware / backup: https://mega.nz/#!APhWya7B!nNrDImupeIaPyPAvIrFxGyyfoZEAIO-DEAy2XFtCDIM
link to TWRP: https://mega.nz/#!NHpBlY5C!RPVpVCUuTslLOrcf_bjL4pBYOGblcrRlN8CQ9I7cIbY
in the TWRP the sensor does not work, control via the otg cable through the optical mouse
after the TWRP firmware you need to boot into it and install the root, otherwise the android system will restore recovery
link to patch root: https://mega.nz/#!0HRHzbia!rX1iMekfYymzSzq0AtTT96-lELMziirBIAF3kpe_BCc
regret to tell, but firmware is odexed.. 80-90%, it accidentally happened that during brief look i saw couple apps from that 10-20% deodexed, the rest has .odex files
I'm expecting my phone today, so I'll post impressions over the weekend. Any news about about a Lineage port?
My s60 issues so far..
Hi, i have a s60 for about 2 weeks now and i can tell its not without issues:
1. Screen comes ON with no reason, as IF somebody tryes to unlock with finger print, it and says "too many attempts, try later" .It happends quite often and it goes every 30 seconds or so.. Then stops.. Half an hour latter starts again... Annoing..
2. Finger print unlocking-hit and miss... Sometimes it unlocks as soon as you touch it, sometimes doesn't work at all..
3. Loud speaker ,again, sometimes on full volume you get loud and crisp sound, even then one of them is fake, but next time, out of nowhere sound becomes so crappy , like from ripped speaker, doesn't take high piches at all, even IF you tune volume half way dawn.. like its broke sudennly.. latter OK again.. That affects sounds, like call or notifications- sometimes its loud and clear, sometimes you just miss them..
4. Calling 2 out of 10-12 calls, -you dont hear them, well you do, but so quite, that you just can't make up the words. And then it fixes itself..
5. Camera is inposibble to focus where you want. It hunts a lot.. In the menu settings for ISO and shutter speed set to auto and greyed, like its there, but you can't change it-gimmick??
Over all-battery life is great, screen is superb with very natural color reproduction, camera is very good then you get it in focus. Dynamic is clear and loud then it works.. Call quality is superb then it works. Never dropped WiFi conection, Bluetooth connects instantly and never had an issue, reception very good.
Hope all thouse problema are software related and can/will be fixed by update, becouse its a nice phone. Love the size of it.
Hi, I have this phone which I bricked by downloading - I guess - the wrong firmware with sp flash tools.
https://www.freebrowsinglink.com/hoot-p20-pro/
The phone is dead. Whenever I try to download, format+download, or do anything for that matter gives me the following error message:
{
"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"
}
Is there anything I could try to save it from salvage? Thanks.
Do you have the correct stock ROM?
Can you get the phone in adb/fastboot?
Hard Bricked Hoot P20 pro Clone
Phone is completely dead. There is no stock rom, nor support website, only a couple of funny looking web pages located in Bangladesh or Burma, or something like that, and they offer roms for p20 pro clone phones. I tried one and I downloaded the software via sp flash tool, because the regular recovery on the phone itself, whenever I tried to re-install, would give a lot of errors after first boot and/or every reset for that matter; it'd say 'UI stopped working', 'clock stopped working' and so on with a whole sequence of error messages rendering the phone useless. So I tried to find something on the internet, but that did not work out the way I hoped for THanks.
Can you get into the recovery mode?
I am not sure what you are saying when you say "because the regular recovery on the phone itself, whenever I tried to re-install". You need to find "Factory Rest" line in recovery mode that would be the first thing to do. It may take going through fastboot mode usually pressing down on the "power button and volume down button" and then maybe go to recovery in menu press power and then press "power button and volume up button" , but it real depends on the phone, but you need to find "Factory Reset"
I know you can't get into the phone but finding out Device name something like n 1awifi or X1995-2, GPU vendor, GPU used, MODEM M632_05.34.01.73R OCEAN_LATAMDSDS_CUSTMODEM M632_05.34.01.73R OCEAN_LATAMDSDS_CUST (this off a Motorola phone but to give you an idea) will help in trying to find a stock Rom that may work or whether the "firmware" you have gotten is appropriate for your phone. Usually, these things are in file name of the rom or "firmware" so you can see if it is the right one.
But to be honest with you if factory reset doesn't work there is little chance you can unbrick your clone phone without the stock ROM and it appears the custom ROMs being sold are buggy or was not the right one, or someone just to making money.
Hoot P20 Pro Clone
Thanks for the response. As said, phone is dead, even the charging icon for the battery isn't showing up anymore. It had Android 5.1 on it and it has a MTK6580A quad core inside. I bricked the phone after downloading Android 7.1 for MT6580 chip set via SP Flash Tool. I can't start recovery, again phone is completely dead.
How can I resolve the 'enable dram fail (4032)' error in SP Flash Tools? Any ideas? Thanks.
Clone_Cat said:
Thanks for the response. As said, phone is dead, even the charging icon for the battery isn't showing up anymore. It had Android 5.1 on it and it has a MTK6580A quad core inside. I bricked the phone after downloading Android 7.1 for MT6580 chip set via SP Flash Tool. I can't start recovery, again phone is completely dead.
How can I resolve the 'enable dram fail (4032)' error in SP Flash Tools? Any ideas? Thanks.
Click to expand...
Click to collapse
Forget the SP Flash Tool because you don't have any compatible ROM to flash to your phone. What you need to do is get into recovery usually hold the power button down then the volume button down and find "Factory Reset". I may require more manipulation of the power button and volume buttons to negotiate through the menu, but hopefully, in your case, the "Factory Reset" line will be on your first recovery page.
The battery died because of the continuous boot loop. If you get that again take out the battery.
You need to recharge the battery either outside of your phone, or you can try throwing the battery in the freezer for a while stick it back into the phone and plug into the USB charger without pressing any buttons. Google tricks to reviving a dead battery.
The recovery should still be working on your phone. Google how to get into recovery for your phone/manufacture. The procedure should be the same for all phone by the manufacturer.
Bricked Hoot P20 pro Clone
Ok, thank you for your suggestions. I did try format all and download in SP Flash Tools several times in the process, doesn't that erase everything from the phone, even recovery?
Again, and I don't know how important that info might be, the phone went dead after I copied Android 7.1 with SP Flash Tool through the upgrade firmware option. The ROM was meant for DooGee Shoot 2 phone, but it has the same SoC, namely the MT6580A, so I thought it might work.
If the battery went dead and won't charge, like you said, it would explain why the battery icon is not showing up any longer. I tried already to open the back, but I couldn't manage. Don't you need a heat gun for that to soften up the glue? Or is there perhaps a different technique?
Thanks.
Some sort of recovery should be there. It is doubtful it was erased.
ROMs not specifically made for a specific phone are unlikely to work or work well. I recently installed a ROM on my phone from a different region but same model of phone. Everything worked except the modem. I couldn't make a call. Easy fix for me though.
A while back I had a tablet where the battery went completely dead, and no charge icon screen, completely black.. I left it plugged into a USB charger. I bought another battery. By the time I got the new battery. The old battery charged fully and is still working today with no problem. So there is still hope for you. I did take the battery out for about ten minutes and put it back in before connecting it to the USB charger. I do not know if that made a difference. I left the back off while charging because I though I would have to replace the battery.
If your cover is glued on, use a hairdryer not a heat gun. A heating pad may work also. There are YouTube videos out there showing how to take off a glued phone back. You can search for how to replace a battery in a Moto G7, they have a glued back and I know there are how to videos. If the back is plastic tabs, you can use a guitar pick or something like that. There are video out there for that also.
Hey to my fellow people of earth !
My tablet suddenly not booting up properly ...
Every time when I use my tablet, I turn it on and when I finish to use it I turn it off (maybe it's the problem?!)
I don't use it too often ... Yesterday It worked normally and today I picked it up, turned it on and I've no fk'n idea why it got stuck on the "Samsung Galaxy TAB S3" logo.. so I tried to do something to make it work...
I tried to go to recovery mode (Home+V up+Power) and since then It always says on the top left corner with a blue color "RECOVERY BOOTING...." and it not get into the ASR (android system recovery)
Then I tried to flash an official firmware Android version 8.0.0 from Germany and it didn't work too...
I tried to flash an old firmware version 7 and I got a failed massage on Odin and FRP block something like that.. on my tablet.
ohh yeah I just remembered that I tried to update it with Kies and Smart Switch
and of course.. I got a "SAMSUNG not supporting this device..." massage.. (Son of a..)
I have no idea what do....
I can't root it 'cause I can't change the OEM and the USB debugging..
I can't even put any file on it since I cant turn it on..
Indeed it's a Weird situation guys.
Someone ?
{
"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"
}
p1234p1 said:
Someone ?
Click to expand...
Click to collapse
I have some questions to help me understand your problem.
You can boot into download (Odin) mode?
When you tried to flash the stock firmware what version of Odin did you use and what were the errors you got when you tried to flash it.
I haven't used the stock recovery for awhile on the tab so could you remind me what happens when you try to get into recovery? Does it look like a dead Android?
@jd1639
Hi.
Yes, I can boot into download mode.
I used Odin3_v3.13.3.
When I tried to flash the stock firmware (T820XXU3BSD1_T820DBT3BSD1_Germany_8.0.0_4)
I got an error massage. Fail massage on Odin and block massage by FRP on my Tablet.
When I try to get into recovery mode, I don't see a dead Android. I just see on the top left corner of the tablet
with blue color a "RECOVERY BOOTING...." massage.
p1234p1 said:
@jd1639
Hi.
Yes, I can boot into download mode.
I used Odin3_v3.13.3.
When I tried to flash the stock firmware (T820XXU3BSD1_T820DBT3BSD1_Germany_8.0.0_4)
I got an error massage. Fail massage on Odin and block massage by FRP on my Tablet.
When I try to get into recovery mode, I don't see a dead Android. I just see on the top left corner of the tablet
with blue color a "RECOVERY BOOTING...." massage.
Click to expand...
Click to collapse
This is what I would do:
Download the firmware again, sometimes you get a bad download.
Try different USB cables, and if your using a PC use the ports on the back, not the ones on the front. Odin can be sensitive to cables and ports.
In Odin flash the BL, AP, and CSC. Don't use the CSC Home. Also, don't have re-partition checked.
Did you ever enable developer mode and enable OEM unlock in it? You'd do this through settings, about tablet, system software and tapping on the build number 7 times.
jd1639 said:
This is what I would do:
Download the firmware again, sometimes you get a bad download.
Try different USB cables, and if your using a PC use the ports on the back, not the ones on the front. Odin can be sensitive to cables and ports.
In Odin flash the BL, AP, and CSC. Don't use the CSC Home. Also, don't have re-partition checked.
Did you ever enable developer mode and enable OEM unlock in it? You'd do this through settings, about tablet, system software and tapping on the build number 7 times.
Click to expand...
Click to collapse
That's the problem, I can't enable developer mode and enable OEM so because of that I always get an error on my Tablet.
I'll try your method tomorrow, Hope it'll work :good:
@jd1639
OK.
I tried to flash two different firmware.
1) T820XXU3BSD1_T820DBT3BSD1_Germany_8.0.0_4File
2) T820XXU1ARA1_T820OXA1ARA1_BTU
When I flashed to first one, I got a pass installation on Odin and my Tablet did a reboot but it still stuck on bootloop and it shows a blue massage on the top left corner.
But, the second one gave me a fail massage on Odin and on my Tablet I got also something like that.
Some pictures of the second attempt :
p1234p1 said:
@jd1639
OK.
I tried to flash two different firmware.
1) T820XXU3BSD1_T820DBT3BSD1_Germany_8.0.0_4File
2) T820XXU1ARA1_T820OXA1ARA1_BTU
When I flashed to first one, I got a pass installation on Odin and my Tablet did a reboot but it still stuck on bootloop and it shows a blue massage on the top left corner.
But, the second one gave me a fail massage on Odin and on my Tablet I got also something like that.
Some pictures of the second attempt :
Click to expand...
Click to collapse
I think you have to wait for 7 full days (168h) 'cos you got locked outside your phone. Read https://forum.xda-developers.com/samsung-a-series-2017/how-to/guide-root-install-twrp-samsung-t3747535
try with 4 file firmware
Sent from my SM-A505F using Tapatalk
Guys ! come on I need help...
SAME
I have the exact same problem and it drives me crazy. I also flashed 2 or 3 times through ODIN, but nothing. Same freaking blue message "Recovery booting"....
p1234p1 said:
@jd1639
OK.
I tried to flash two different firmware.
1) T820XXU3BSD1_T820DBT3BSD1_Germany_8.0.0_4File
2) T820XXU1ARA1_T820OXA1ARA1_BTU
When I flashed to first one, I got a pass installation on Odin and my Tablet did a reboot but it still stuck on bootloop and it shows a blue massage on the top left corner.
But, the second one gave me a fail massage on Odin and on my Tablet I got also something like that.
Some pictures of the second attempt :
Click to expand...
Click to collapse
Got? I have the same mistake
Had a similar problem with my T820, sorry I haven't found a solution as yet. One day the tablet went to a black screen, frozen. After a full charge was able to soft-reset and it booted fine, but decryption took ages, and then on PIN security screen the tablet was locked.
Booted into recovery, and tried to do a factory reset - but there are messages about missing partitions, so the delete starts, but never finishes.
Finally, downloaded official roms for v9 and v8 - but the odd thing, in Odin (re-partition unchecked) if I use default CSC (not CSC Home) it fails when trying to remove userdata. If I use CSC Home, then it passes but on reboot it goes into recovery and a blue "erasing screen" appears, and just endlessly tries to erase until the battery is flat.
Other similarity... region is Germany, so could there have been an update which has bricked devices here? Any advice appreciated... should I try using re-partition in Odin as well, as there could be some partitioning based on the error messages?
Get the tablet into recovery mode (power+vol UP+home), then select the option to wipe data/cache.
Then boot the tablet into download mode (power+vol DOWN+home)
In ODIN, only load the AP and BL files. Nothing else. Then start the process. DO NOT load the CSC or HOME CSC files.
I was having the same issue for almost a year. I gave up for 6+ months. Then I spent the last couple days trying to get the unit out of the boot loop it was stuck in (Samsung S3 start screen shows, then it attempts to go to the recover mode screen, then turns off, then turns back on and repeats the process until the battery died). I tried to reload the firmware through ODIN (either 3 or all 4 files) but the tablet would fail to install the "update" once it restarted. It would fail at 32%. I read someone else in this forum only loaded the AP and BL files and ended up working. Make sure your tablet is fully charged.
Vchenz84 said:
Get the tablet into recovery mode (power+vol UP+home), then select the option to wipe data/cache.
Then boot the tablet into download mode (power+vol DOWN+home)
In ODIN, only load the AP and BL files. Nothing else. Then start the process. DO NOT load the CSC or HOME CSC files.
Click to expand...
Click to collapse
Thanks for the reply, having spent many more hours on this I'm pretty sure it's a fault in the actual memory. It comes down to the userdata.img...
I've tried with Odin 3.13 the following
- re-partition: same issue, it fails when flashing userdata.img
- re-partition + nand erase... here it gets interesting, as it fails just as it starts, and on the tablet it displays "erasing userdata", so it seems even with nand erase set, the tablet refuses the clear this data. It also would explain why after a flash with HOME_CSC (which succeeds because it doesn't have a userdata.img) the boatloader goes into an erase loop, as it's probably trying to clear userdata.
I've got no idea what could cause this, corrupt memory chips? or just buggy buggy software - but I'm guessing Samsung really don't care too much and don't need to since all devices are out of warranty. Shame really!
woke up to the same issue on my tablet out of nowhere
squatticus said:
woke up to the same issue on my tablet out of nowhere
Click to expand...
Click to collapse
Mind me asking which region @squatticus...
parherik said:
Mind me asking which region @squatticus...
Click to expand...
Click to collapse
US
A couple of weeks ago, i found a video titled: <<34C3 - eMMC hacking, or: how I fixed long-dead Galaxy S3 phones>>
This guy made an SD Card with a code inside, and basically "revived" a dead Galaxy S3. He also explains that eMMC is the one at fault if your phone is stuck in bootloop. Now i don't know anything about how this works, I whish i could just knew how to alter his code, I'll try to text him and tell him if it's possible to try it on my Tab S3, since i have literally tried everything to revive it.
If any1 here knows how to do it, pls pls pls help us out!!!!
I might be late for the party but i got the same issue out of no where, sent it to Samsung and they called me saying they need to replace the PCB (Main Board) guess what, in the last 2 years they replaced it twice coz i had a wifi not turning on at all. Now they wanna charge me 250$ , guess i am happy now coz i am getting rid of this garbage tab never seen a laggy piece of **** like it and nothing came out of but headaches.
My 5 years old ipad air 2 running like a champ since day one until today, not showing any sign of aging and still getting updates.
Tbh, i think the worst devices samsung ever had gets the number 3. Tab S3 and the Galaxy S3.
My advice to anyone who read this, save your time and money, never buy android tabs especially Samsung, spend a few more bucks and get the ipad which will last forever. PS: Without mentioning the huge gab of performance as IpadOS beats the **** out of any android tab