Related
Continuing my quest for confirming an unlocked/locked bootloader, I have stumbled across a key combo for getting into download mode! When the phone is off, hold the volume up button and plug in the micro usb cable, the phone should then boot up (on its own, do not touch the power button) to a screen with a grey box with a down arrow that says download mode. For anyone that used to own a Samsung Galaxy S phone, this mode was the primary mode for flashing roms via Odin and Heimdall. Now we just need a recovery rom and flashing software (possibly [AIO] ROMTools, I will fiddle around with it tonight).
Confirmed on Bell Optimus LTE, unit must be off, hold up while plugging in USB cord.
gte460z said:
Continuing my quest for confirming an unlocked/locked bootloader, I have stumbled across a key combo for getting into download mode! When the phone is off, hold the volume up button and plug in the micro usb cable, the phone should then boot up (on its own, do not touch the power button) to a screen with a grey box with a down arrow that says download mode. For anyone that used to own a Samsung Galaxy S phone, this mode was the primary mode for flashing roms via Odin and Heimdall. Now we just need a recovery rom and flashing software (possibly [AIO] ROMTools, I will fiddle around with it tonight).
Click to expand...
Click to collapse
This is great news! I've been needing to re-flash the stock ROM since day one (when I hosed my root with a bad busybox)...
Very nice find... I had been able to get into download mode before, but I didn't realize it was the usb connection that allowed it.
If you look in some of the other threads you will see that I have been able to locate the boot and recovery partitions - just 'standard' emmc partitions. I have pulled the data off the device and unpacked them so that I am able to look at the data within the partitions. Next is to start to understand what is inside the files - mainly init.rc and the other .rc files.
Currently I think part of the lack of recovery for us has to do with a line in init.rc:
service adbd /sbin/adbd recovery
disabled
Something tells me this will disable the recovery capabilities for the phone... but still looking around to figure it out. Will keep everyone posted.
Please do! Sounds like we are making progress as a whole!
great news guys!
thx 4 ur hard work!
hope ur next good news~
Wonderful news we are getting this past week!! Much progress has been done I'm getting so excited at where all this will lead us to Glad to be part of a sub-forum with tons of fiery passion and dedication. I'm not much of a help since I'm not good with any of these things, but I'll contribute in any way possible
Just got this phone for Christmas, but they were out of stock at 2 nearest stores to me. Have to wait a day or 2 for it to be shipped alas.
If you set it so that start adbd in recovery is enabled, what happens when you use ROM Manager to boot into recovery? I tried booting into recovery without editing the init.rc and I got a little Android guy with an open box and an arrow coming out for a sec, but then it kicked me out by rebooting.
Sent from my LG-P930 using xda premium
I will be attempting to do that some time this evening. Before I attempted it I wanted to be sure I wasn't going to be stuck with a brick. It will also let us finally figure out if out bootloader is locked or not.
schwin97 said:
I will be attempting to do that some time this evening. Before I attempted it I wanted to be sure I wasn't going to be stuck with a brick. It will also let us finally figure out if out bootloader is locked or not.
Click to expand...
Click to collapse
Good luck and God Speed Sir!! Bring home the bacon!
So has anyone figured out what we can use this mode for?
If it means anything, that was the mode I had it in while I flashed the SU640 rom.
Good to know, I figured it was the mode that the LG tool used to flash the phone.
I am currently trying to fix a friend's Xperia Play r800a. It seems to be having a few different problems and together they are making it all difficult to get it going again. First off I have no real knowledge of toying with an Android phone. I browsed some threads on here, used Google and tried to use Flashtool to get the original operating system on it but all were a no go. I'll try and describe the problems to the best of my abilities and maybe someone can offer some help.
This is what I know from what he remembers he did to the phone. He said that the phone started t only boot to the Sony logo and then it would hang until the battery died or the phone was reset. If plugged in with a wall charger then it would allow him to get to the screen where he would enter his password but the touch screen wouldn't work. He then flashed it using Flashtool and at that point it would boot to a black screen and that's it.
-It hangs on a black screen, no logo or anything is present and it happens regardless of whether it is plugged into a wall charger or not.
-It is not found when plugged into the USB port (Windows 7 PC) and shows up as an unknown device. After a few minutes it is found by the PC but sometimes will randomly go back to an unknown device.
-I sometimes get a red light which blinks three times when I press the power button on the phone. I am currently charging it to see if it was a matter of being a dead battery or something worse (I heard it could be a hardware failure).
Any suggestions would be appreciated.
My Xperia Play has done This I asked a Mate (Jinx13) He said Il do a hardcore Testpoint process. After I have done this My Phone will Vibrate and Nothing I was Playing Rayman today and it Locks and Hardware Keys Do Not respond.
Then Touchscreen Stopped Working. Indeed This is a Hardware Failure I have got this and Re-Flashing with Blinking SETOOL2 and Resseting it Wouldn't work. I Then Re-Locked By fastboot SIM and Bootloader (Maintained DRM) and Now Dowloading R800i O2-UK From SETOOL Support and 3-UK one and I will Upload them for US people for Warranty they Become indeed handy . I now Am Going to O2 shop I was Running 2.3.4 .42 GENERIC.But I am Not allowed to Give you the FW's Only by Re-Uploading I Can. Anyway My Brave Soldier Died (Hardware Failure) Its the Screen Components.Im Not Rooted anymore and Re-locked with S1-Tool.
If this happens to you My advice is Dont Flash Alpha ROM's They can make Your device Coo Coo. And OC can Damage.
Basically I boot My phone with a 3600MAH Mugen Battery 89% Battery From the Last time It was on. Im afraid your friends Phone is Dead Maybe a Hardware Failure Most Likly and I am now Officialy Out of the Game.
But O2 Gave me 3 Year warranty!!!!! For £100 When I Purchased it. So I am Going to O2 in Stevenage and Say this What actually happend:
"I Purchased My Xperia Play on August 17th Through Online Store ; I have never had a Problem With My device Untill This week : I have had these Issues:
*Touchscreen Wont respond Cleaned Several Times.
*Random Reboots
*Red Light when Phone had 50%+ Battery
*Would Take 6 Battery Pulls to Turn on (Would Only turn on Earlier during the week)
*Lagged In games.
*Running O2 Branded Software
*No Screen Brightness or Signs of Working Screen.
*Would Not charge Unless turned On
*Camera Would Not work Unless Wifi Was not on I dont know why?
So Basically This Phone had a A fault since Day one I always had Camera Fails.
bluetoon said:
I am currently trying to fix a friend's Xperia Play r800a. It seems to be having a few different problems and together they are making it all difficult to get it going again. First off I have no real knowledge of toying with an Android phone. I browsed some threads on here, used Google and tried to use Flashtool to get the original operating system on it but all were a no go. I'll try and describe the problems to the best of my abilities and maybe someone can offer some help.
This is what I know from what he remembers he did to the phone. He said that the phone started t only boot to the Sony logo and then it would hang until the battery died or the phone was reset. If plugged in with a wall charger then it would allow him to get to the screen where he would enter his password but the touch screen wouldn't work. He then flashed it using Flashtool and at that point it would boot to a black screen and that's it.
-It hangs on a black screen, no logo or anything is present and it happens regardless of whether it is plugged into a wall charger or not.
-It is not found when plugged into the USB port (Windows 7 PC) and shows up as an unknown device. After a few minutes it is found by the PC but sometimes will randomly go back to an unknown device.
-I sometimes get a red light which blinks three times when I press the power button on the phone. I am currently charging it to see if it was a matter of being a dead battery or something worse (I heard it could be a hardware failure).
Any suggestions would be appreciated.
Click to expand...
Click to collapse
okay lol i don't know if that second post helped but is the phone unlocked? by any chance if it is, you can never really brick your xperia, from experience i kept flashing re flashing cusom kernal all day i get the same loops etc, but always fixable, also flash tool should fix your phone if that is you got the right ftf file for the brand like i have verizon and it have a verizon.ftf file, other than that i need more info about the phone not how it bricked, like what was it running at first etc. Try sony software reflashing repairing if that doesn't work use flashtool and see if you get an error with that
I cant enter fastboot or recovery lol
Xperia4life said:
I cant enter fastboot or recovery lol
Click to expand...
Click to collapse
lol xD oh danm only possible way i think is to try flash tool and downloading the ftf file for your phone and let me know if you get any errors
biggyhead said:
lol xD oh danm only possible way i think is to try flash tool and downloading the ftf file for your phone and let me know if you get any errors
Click to expand...
Click to collapse
my phone is having the exact same problem, it wont recover through pc companion and flashtool wont even work cause I cant get my phone into flashmode.
are there any other tricks that might get my beast running again?
NevErSn0w said:
my phone is having the exact same problem, it wont recover through pc companion and flashtool wont even work cause I cant get my phone into flashmode.
are there any other tricks that might get my beast running again?
Click to expand...
Click to collapse
How are you trying to get into Flashmode?
Sent from my Slider SL101
I was too, until yesterday.
Why was I unsure?
Because I was afraid of loosing warranty of such an awsome and expensive phone.
What was the reason that I rooted it anyways?
I wanted to flash the latest stock ROM from Germany to my Austrian phone via Odin and so I had to make a full wipe.
Then I thought that I wouldn't root it if I didn't do it now, because i hate to backup and restore everything.
If you stay at stock ROM and keep the stock recovery, I think you won't loose your warranty if anything happens to the phone.
If you flash a custom kernel, you have to set Triange Away to reset the flash counter on each boot (only if your kernel supports it).
I read a lot about it and decided to root it with CF Auto Root (Step 1 in that post), because it keeps the stock recovery.
AFAIK the kernel of the CWM recovery isn't SDS proove. And Nandroid Backups are not that important for me, because I don't plan to change the ROM often.
I also have read a lot about custom kernels. They unleash the full power of android!
So after reading the latest change log entries and lots of posts in the Perseus Kernel Thread, I decided to flash this kernel using Odin.
After wiping dalvik cache with Andromizer (since I don't have CWM) and wiping battery stats using Battery Calibration Free (since I don't have CWM), I felt like Alice in Wonderland!
MY PHONE WAS FAST AS HELL!
Then I found a new app called STweaks and I couldn't stop to grin.
All I thought was: Why didn't I do this earlier????
So if you are unsure about rooting your phone, I hope this article helped you and you begin rooting your phone now.
muena90 said:
If you stay at stock ROM, keep the stock recovery and set Triange Away to reset the flash counter on each boot I think you won't loose your warranty if anything happens to the phone. (Please correct me if I am wrong)
Click to expand...
Click to collapse
If you are having stock recovery and kernel, no need to set reset countr at every boot, you need it just once then you can uninstall Triangle away.
You need to reset counter on every boot only if you have custom recovery/Kernel.
Again you need to have support in your custom kernel to use this option(reset counter at every boot)
dr.ketan said:
If you are having stock recovery and kernel, no need to set reset countr at every boot, you need it just once then you can uninstall Triangle away.
You need to reset counter on every boot only if you have custom recovery/Kernel.
Again you need to have support in your custom kernel to use this option(reset counter at every boot)
Click to expand...
Click to collapse
Thank you, I just updated my post.
As a techie who knows he's unlikely to end up bricking it (and accepts that if I do it's probably my fault for doing something stupid) I'll not be intimidated by Samsung not to root, just like I wasn't intimidated by HTC, and I'm sure it's probably not me (but rather, non-techies) who they're trying to intimidate.
Besides, from what I was reading you just have to put it back to stock to get your warranty back. But even if a fault developed that bricked it (and not of my own doing, but I'd never overclock or anything anyway and am unlikely to do anything stupid), as I'm in the UK and we have a lot of consumer rights, I'd just keep parroting the Sale of Goods Act at them and possibly threatening a small claims court until they got the message
It's like rooting any other Android phone: naturally they won't help you with it, and I can see where they're coming from in that they won't do warranty returns if a non-technical person tries it and screws it up and then claims that it's faulty. That's what they mean - not genuine hardware faults, but being asked to cover a bad flash. So basically: only do it if you're confident, and it's at your own risk if you don't have a clue what you're doing. But it's quite difficult (if not impossible?) to permanently brick to the point where you can't even get to ODIN download mode, it's just that a lot of people think "won't boot into a working OS" means "bricked" and throw the towel in. (Personally I think it's difficult to even "brick" the OS as long as you take your time and read the instructions properly). That's where you can get unstuck as there's nothing actually wrong with the phone's hardware you just don't know what you're doing and that's where they're within their rights to say "no" to helping you out with a free unbricking or replacement. Even within consumer laws.
There's less reason to be put off than with a HTC phone, as the bootloader isn't locked so you don't have to go through the tedium of a full wipe and having to download all your apps again.
I do find that people who develop tools and tutorials tend to overcomplicate it with paragraphs of instructions and complex UIs full of a billion functions and tabs. Here's how I do it in Arch Linux:
Install Heimdall.https://aur.archlinux.org/packages/heimdall/
Get CWM Recovery: http://www.clockworkmod.com/rommanager
Download the touch version for Samsung Galaxy Note 2 (HSPA+)
Get CWM-SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Copy it to the SD storage.
To copy to SD storage if MTP isn't working in Arch:
Code:
sudo pacman -S libmtp
mtp-detect
mtp-connect
mtp-sendfile UPDATE-SuperSU-vx.xx.zip UPDATE-SuperSU-vx.xx.zip
Plug phone into PC
Turn it off
Hold down Volume DOWN, home and power until download mode screen appears. Press volume up to accept flash mode warning.
sudo heimdall flash --no-reboot --recovery recovery-clockwork-touch-x.x.x.x-n7100.bin
This should work, if not try a different USB port, try re-entering download mode etc.
While still at the download mode screen (if you reboot completely it'll re-flash recovery to stock) hold Volume UP, home and power until the Samsung logo repeats itself then let go, eventually CWM Recovery will appear.
Install zip from SD card
Select the CWM SuperSU zip
Reboot
That's it!
Nothing more complicated than that. In Windows you just basically use ODIN to do the same thing, but this is one of those occasions where things are actually easier to do in Linux than Windows.
Edit: Obviously you follow the above at your own risk and should learn how everything works - I'm just sharing my own notes to show how easy it can be.
Cloudane said:
As a techie who knows he's unlikely to end up bricking it (and accepts that if I do it's probably my fault for doing something stupid) I'll not be intimidated by Samsung not to root, just like I wasn't intimidated by HTC, and I'm sure it's probably not me (but rather, non-techies) who they're trying to intimidate.
Besides, from what I was reading you just have to put it back to stock to get your warranty back. But even if a fault developed that bricked it (and not of my own doing, but I'd never overclock or anything anyway and am unlikely to do anything stupid), as I'm in the UK and we have a lot of consumer rights, I'd just keep parroting the Sale of Goods Act at them and possibly threatening a small claims court until they got the message
It's like rooting any other Android phone: naturally they won't help you with it, and I can see where they're coming from in that they won't do warranty returns if a non-technical person tries it and screws it up and then claims that it's faulty. That's what they mean - not genuine hardware faults, but being asked to cover a bad flash. So basically: only do it if you're confident, and it's at your own risk if you don't have a clue what you're doing. But it's quite difficult (if not impossible?) to permanently brick to the point where you can't even get to ODIN download mode, it's just that a lot of people think "won't boot into a working OS" means "bricked" and throw the towel in. (Personally I think it's difficult to even "brick" the OS as long as you take your time and read the instructions properly). That's where you can get unstuck as there's nothing actually wrong with the phone's hardware you just don't know what you're doing and that's where they're within their rights to say "no" to helping you out with a free unbricking or replacement. Even within consumer laws.
There's less reason to be put off than with a HTC phone, as the bootloader isn't locked so you don't have to go through the tedium of a full wipe and having to download all your apps again.
I do find that people who develop tools and tutorials tend to overcomplicate it with paragraphs of instructions and complex UIs full of a billion functions and tabs. Here's how I do it in Arch Linux:
Install Heimdall.https://aur.archlinux.org/packages/heimdall/
Get CWM Recovery: http://www.clockworkmod.com/rommanager
Download the touch version for Samsung Galaxy Note 2 (HSPA+)
Get CWM-SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Copy it to the SD storage.
To copy to SD storage if MTP isn't working in Arch:
Code:
sudo pacman -S libmtp
mtp-detect
mtp-connect
mtp-sendfile UPDATE-SuperSU-vx.xx.zip UPDATE-SuperSU-vx.xx.zip
Plug phone into PC
Turn it off
Hold down Volume DOWN, home and power until download mode screen appears. Press volume up to accept flash mode warning.
sudo heimdall flash --no-reboot --recovery recovery-clockwork-touch-x.x.x.x-n7100.bin
This should work, if not try a different USB port, try re-entering download mode etc.
While still at the download mode screen (if you reboot completely it'll re-flash recovery to stock) hold Volume UP, home and power until the Samsung logo repeats itself then let go, eventually CWM Recovery will appear.
Install zip from SD card
Select the CWM SuperSU zip
Reboot
That's it!
Nothing more complicated than that. In Windows you just basically use ODIN to do the same thing, but this is one of those occasions where things are actually easier to do in Linux than Windows.
Click to expand...
Click to collapse
Fully confirm!
It's more likely that your phone dies because it decides to take a round in the washing machine (like my last one) than you brick it.
I first thought about providing a fool-proove step by step manual how to root your Note 2 and flash a custom kernel.
But then I thought that if anyone wants to root his phone, he should read into it himself, so he knows what he's doing.
Rooting is easy when you understand ehat you are doing. When my brother bought his Kindle Fire I discover the wonderful world of Android so I came up with an idea, root my brother's Kindle, my brother let me do it because as we live in South America the Kindle not longer have guarantee, so I plug the tablet to my PC and began the process. I was so nervous that I committed a lot of mistakes that result in the Kindle bricking twice. At the third try I made it and we began installing ROMs and Kernels, the I bought the little Galaxy Y. That phone was the most modified think I ever see. I installed like 20 custom ROMs, Kernels Scripts and anything I found in XDA. Then my father see my affection to Android and borrow me the Galaxy Note II so in a big step I remember how great was rooting benefits and thats why I rooted the phone, now my other brother is buying a Nexus 4 and we just can't stop talking about root benefits.
Thats a long story
Sent from my GT-N7100 using Tapatalk HD
Can anyone help me with this problem?? I tried many ways but there isnt anything possible. The community either ignores me or gives me a simple answer. Can anyone just give me a suggestion of what i cant do?
You can't do anything with it by the looks of things, it's gone.
me too.....
On the same boat but mine is being recognized by my PC.
Same here... some extra info.. but still broken.
It happened yesterday. I have the H812 Canadian version. It just was suddenly, I wake up and pull it from the charger, read some mails during breakfast, go to work and then the screen didn't turn on. Holding the power button did nothing.
- Pull the battery, put it back, nothing.
- Then maybe I though maybe the phone didn't charged properly overnight and the battery died. I plug the charger and the battery logo pop-up 2 seconds later it boot up on the LG animation logo. It goes stuck loping there.
- After 30 minutes, holding power button did nothing, pull the battery. Always on the charger put the battery back and it immediately went to Recovery Mode and at the end showing "fastboot mode". What!!! I thought this phone bootloader is locked.
- I unplugged for the power and put in on the computer and it was recognized as "Marshall phone". I tested "fastboot devices" command and it was recognized. Well it could be recovered if I had a image that I could applied.
- I tried to applied a previous download KDZ "H81210H_00.kdz" even that my phone was already on "v10n". But fastboot didn't liked the kdz file format.
- Previously also I did a backup of the system partition but also the format is incorrect for fastboot.
- So no available files that I could apply on fastboot.
- I removed the usb and battery put it back. Black screen. Nothing.
- Plug the phone without battery on the USB and for my surprise the computer still recognized as "QHUSB_BULK" but not recognized driver. Which reading around, I understand is a Qualcomm low level mode to start up programming a device, but no information of how to do it.
- To go back fastboot, I had to simultaneously plug the USB and insert the battery at the same time. Sometimes even the fastboot gives an error that could start. Which it makes me think the phone ROM has a major corruption and it's booting on the emergency bootloader.
So, I didn't have time to keep playing around to see if I could do anything else. I drove to a Fido store and drop it to send it to LG for repair.
This is my first brand phone out of Nexus, I'm really disappointed with LG (actually this will be the case with any major Android brand phone).
- First there used to be a way to recover the current KDZ, now they closed the path.
- Later, only offers unlock boot loader on one model that is not in north america.
- No fastboot recovery images. Zero, nada.
So, many times I had bricked my Nexus phones by tweaking and playing around, and it always there is a way to recover it. The LG G4 brick itself on my pocket and I feel helpless to try to recover it. Even my wife iPhone's I have been able to restore them by downloading the full recovery image.
I'm seriously thinking resell my LG G4 as soon as it's back and go back to Nexus phones (5X).
tacua said:
It happened yesterday. I have the H812 Canadian version. It just was suddenly, I wake up and pull it from the charger, read some mails during breakfast, go to work and then the screen didn't turn on. Holding the power button did nothing.
- Pull the battery, put it back, nothing.
- Then maybe I though maybe the phone didn't charged properly overnight and the battery died. I plug the charger and the battery logo pop-up 2 seconds later it boot up on the LG animation logo. It goes stuck loping there.
- After 30 minutes, holding power button did nothing, pull the battery. Always on the charger put the battery back and it immediately went to Recovery Mode and at the end showing "fastboot mode". What!!! I thought this phone bootloader is locked.
- I unplugged for the power and put in on the computer and it was recognized as "Marshall phone". I tested "fastboot devices" command and it was recognized. Well it could be recovered if I had a image that I could applied.
- I tried to applied a previous download KDZ "H81210H_00.kdz" even that my phone was already on "v10n". But fastboot didn't liked the kdz file format.
- Previously also I did a backup of the system partition but also the format is incorrect for fastboot.
- So no available files that I could apply on fastboot.
- I removed the usb and battery put it back. Black screen. Nothing.
- Plug the phone without battery on the USB and for my surprise the computer still recognized as "QHUSB_BULK" but not recognized driver. Which reading around, I understand is a Qualcomm low level mode to start up programming a device, but no information of how to do it.
- To go back fastboot, I had to simultaneously plug the USB and insert the battery at the same time. Sometimes even the fastboot gives an error that could start. Which it makes me think the phone ROM has a major corruption and it's booting on the emergency bootloader.
So, I didn't have time to keep playing around to see if I could do anything else. I drove to a Fido store and drop it to send it to LG for repair.
This is my first brand phone out of Nexus, I'm really disappointed with LG (actually this will be the case with any major Android brand phone).
- First there used to be a way to recover the current KDZ, now they closed the path.
- Later, only offers unlock boot loader on one model that is not in north america.
- No fastboot recovery images. Zero, nada.
So, many times I had bricked my Nexus phones by tweaking and playing around, and it always there is a way to recover it. The LG G4 brick itself on my pocket and I feel helpless to try to recover it. Even my wife iPhone's I have been able to restore them by downloading the full recovery image.
I'm seriously thinking resell my LG G4 as soon as it's back and go back to Nexus phones (5X).
Click to expand...
Click to collapse
Look at the Canadian Thread in the general section, there are some direct links to kdz's there.
Here you go
http://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449
Done that
mb_guy said:
Look at the Canadian Thread in the general section, there are some direct links to kdz's there.
Here you go
http://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449
Click to expand...
Click to collapse
I had lurked this forums for 3 year now, and until now I signed up to post my experience. So yeah, I have looked on this forum and other sites for the correct KDZ. If you look careful on that post (as I did) that latest full LP version KDZ is 10h, which already have it for a while. However when this happened to my phone, it was already on 10n which is the version I expect to find somewhere to be able to recover my phone. Recently, I see that is available version 20e but that is already MM, I want to observe how it behave on the community before I decide to go there.
No matter what is the case, the phone was sent for repair. I think mine when under the worst case scenario of the so much mentioned bootloop. So much, that it even opened the bootloader and show me the fastboot prompt, although that the Canadian version is locked.
For my experience with the Nexus, they come with two bootloaders, the normal that can be updated locked and unlocked and a emergency bootloader that is available when the device is almost bricked and the normal bootloader is borked. Finally there is a low level manufacturer flashing that use the OEM SOC application to put the initial ROM. In the past I have been able to play with the Rockchip and the Nvidia Tegra 3, applications at that level. So those devices are simple "unbrickables". Low level Qualcomm (QHUSB_BULK) flashing is barely mentioned on the net, no process detailed, no application available so far that I can find.
My experience with LG so far is like buying a PC with installed OS, no recovery CDs, no website to download the recovery, no access to the BIOS, no "normal" human soul is allowed to create a full backup of the HD without going on a major hackaton with not assurance that what you get will work in future case of emergency. If something happens to the OS when you are out of warranty... you are royally screwed.
Guys try the oven method it may work. Some are saying it lasted 24 hrs others say its still active. It may be dangerous but worth a shot since no one else is taking action on this fix.
Also my phone was just rooted. At that time I wasn't trying to do anything with modifying but just using instagram.
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
You probably going to get a better help at TAB S2 board this is for the tab S1.
If it is hard bricked there is JTAG methods that can help, just need to find one for your device, not easy though.
But all I can do is share my experience with something like this, in a more "cheap" way than JTAGs, dunno if it helps:
I never had a similar problem on the tab S. But in the past a galaxy player 5.0 of mine had a very similar problem (as far I remember the screen just powered the back light but without any letters or simbols)
in 2012, I bricked it trying to mount a swap partition (280mb RAM ftw) accidentally pointing the wrong partition, and got the entire internal storage corrupted.. everything.. system, bootloader, recovery etc
My player was turning on only connected to a USB or charger, like yours. in fact It was hard bricked
I was able to recover it using Linux (because it is the only system able to communicate with the bricked device I had)
The problem is that everything need to be very specific, for example I used a software made for the galaxy s1 to "revive" my player 5 (both have the same hardware) it just made the device be detected via ADB. So I needed to prepare a SD with the same size as the internal storage (in this case 8gb) using the Linux terminal to mount in the SD an exactly schematic of the internal memory using a dump of another device that a xda user shared, (the dump was empty only with the bootloader, recovery etc) but it still had 8gb decompressed. So after that I used ADB to push the SD card content to the internal memory. And it get back to life \○/
Well.. it took me 1 week with a guide!! On the trial and error method. But it worked.. not perfectly, I get bootloops every time I try to flash a rom via Odin, but recovery works, and I have the device working until today
Hi, I Greatly appreciate your reply and advice. Think tho that your solution is a bit beyond my know how I know a little about ADB etc but i would have difficulties in compiling necessary files to sideload. Also many tanks for the link din't realise. Thanks Pal!
Alpha1BA said:
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
Click to expand...
Click to collapse
If you can get it in to download mode you can flash stock rom back on it.......refer to xda samsung tab s2 for more details on this........
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Alpha1BA said:
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Click to expand...
Click to collapse
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
stinka318 said:
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
Click to expand...
Click to collapse
Stinka ure a superstar (atm!) I did as you suggest to no avail but I noticed a slight increase in the time it took to start rebooting again. I do not know which buttons did this but some 20 later it lasted long enough for me to be able to flash twrp. Now i havent actually tried that as yet as i wanted to check with you first... I have the battery logo on screen, i tried recovery and it started as it should but then rebooted, now im unsure at this time whether the battery is almost dead or not so i got it on charge and have the grey battery with a white flash inside... is this what i want for now until its charged? if so i'll keep you informed thamnks more than u know if uve helped me fix this, the reason i was flashing was because when i received it (no warranty!!) the screen sometimes flickered and it would constaly end up rebboting after digging around re that im lead to believe it need a new battery and for the connecting wires to be resoldered. Anyways thanks again n as I say i'll keep this updated
Cheers
Tony
one of the probs i hab/have with this unit is that it takes approx a day to fully charge!!! when i received it the screen flickered on the odd occasion but it was rebooting much more frequently. It came with stock n not messed with previously (i new this prior to purchase so got it for right price thinking it only needed flashing, how wrong was I!!!) so I flashed and encountered the above mentioned problems! thanks to stinka I surprisingly managed to flash a recovery... now provided all goes to plan, which rom would one suggest for stability and generally hassle free and prusuming the aforementioned probs, rebooting etc are still there what could i try to stop that? other than a debloated stock I found Lineage an excellent rom but still the problems got so bad the unit became unusable and was lucky not to go out the window. Im thinking do i start with a replacement battery and check the wires etc or could this still be a software issue??
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
RoIlingThunder said:
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
Click to expand...
Click to collapse
Thanks for that!!!
Tony
does look somewhat OTT!!!
will i have to odin stock first then flash rom i want or will it go straight from first flash via twrp considering there is absolutely nothing on phone at mo apart from twrp.
Alpha1BA said:
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
Click to expand...
Click to collapse
My guess is your issue is lack of charge in the device. That's the reason for the flashing failure and the reboot loop with the firmware error.
Bang it on charge for a while then irrespective of what it's doing, whether it's looping or not, hold POWER + HOME + VOL DOWN until download mode appears.
Reflash the stock firmware with odin.
swapped battery and reflashed stock via odin. It has helped although the issues are all still there its just they happen less frequently which doesnt mean its any less frustrating.