Related
I upgraded to ICS official version with official update that claimed to fix reboot issue.....it didnt so I tried evolver 1.3 and 1.3.1 and got random reboots and power offs too.
I had enough so I reverted to revolver 3.11.1 and was still having reboots even though I did full wipes. So I ran the super wipe script which kills all ? and I am still getting reboots and power offs so what else can I do ? some have said that its the ICS bootloader that has screwed everything so how can I get the HC bootloader back ? Or any other suggestions?
When I found myself in this situation, I found that if I NVFlash a stock honeycomb image first, all is stable again.... I posted a 10 step guide to return to Honeycomb, but you can only NVFlash with theolder Transfomers - is you device NVFlash'able?
Sent from my Transformer TF101 using Tapatalk 2
still on the icys bootloader?
Sent from my Transformer TF101 using XDA Premium HD app
If you were willing to flash a custom ROM, you probably might as well also try Guevor's custom kernel. A bit late now, since you already went back to Honeycomb.
jtrosky said:
When I found myself in this situation, I found that if I NVFlash a stock honeycomb image first, all is stable again.... I posted a 10 step guide to return to Honeycomb, but you can only NVFlash with theolder Transfomers - is you device NVFlash'able?
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Thanks I have not tried that yet.
I have B60 so I can nvflash.
As far as I can tell the main issue with ics is it doesn't like deep sleep because the guvnor kernel disables deep sleep which I guess uses more battery power well thats what I found with version 14 and I still had 1 reboot too.
Thanks for advice guys.
Do you have a link for guide ?
grandmaster_b said:
Thanks I have not tried that yet.
I have B60 so I can nvflash.
As far as I can tell the main issue with ics is it doesn't like deep sleep because the guvnor kernel disables deep sleep which I guess uses more battery power well thats what I found with version 14 and I still had 1 reboot too.
Thanks for advice guys.
Do you have a link for guide ?
Click to expand...
Click to collapse
Search jtrosky's forum posts for that guide.
Here is a link to the quick 10 step guide I put together real quick. Links to stock firmware and root'ing util are provider there as well...
Good luck!
http://forum.xda-developers.com/showthread.php?p=24576480
Sent from my Transformer TF101 using Tapatalk 2
jtrosky said:
Here is a link to the quick 10 step guide I put together real quick. Links to stock firmware and root'ing util are provider there as well...
Good luck!
http://forum.xda-developers.com/showthread.php?p=24576480
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot I got the file and will nvflash back to old faithful HC until they solve this rebooting nonsense
Does the nvflash replace the ICS bootloader ? because I think thats all that could be left causing the issue from my ICS update ? So just wonding how it is going to fix the reboot issue by flashing..........not doubting it does but just wondering how.
grandmaster_b said:
Thanks a lot I got the file and will nvflash back to old faithful HC until they solve this rebooting nonsense
Does the nvflash replace the ICS bootloader ? because I think thats all that could be left causing the issue from my ICS update ? So just wonding how it is going to fix the reboot issue by flashing..........not doubting it does but just wondering how.
Click to expand...
Click to collapse
It does replace the bootloader, although, we've done some testing that also suggests that the bootloader is NOT what it causing the issues in ICS...
I wish I knew what the difference was - keep in mind that there are like 15 or 16 partitions on the iternal memory. NVFlash re-creates them all, I believe, whereas most CWM packages only flash a few of those partitions.
However, I agee - if we can determine what NVflash does differently than CWM when flashing Revolver, it would be a big help in determining where the problem is!
Multiple folks have reported success with the NVFLash method (I haven't seen anyone say that it hasn't worked). I actually learned of it from another post on the forum myself....
jtrosky said:
It does replace the bootloader, although, we've done some testing that also suggests that the bootloader is NOT what it causing the issues in ICS...
I wish I knew what the difference was - keep in mind that there are like 15 or 16 partitions on the iternal memory. NVFlash re-creates them all, I believe, whereas most CWM packages only flash a few of those partitions.
However, I agee - if we can determine what NVflash does differently than CWM when flashing Revolver, it would be a big help in determining where the problem is!
Multiple folks have reported success with the NVFLash method (I haven't seen anyone say that it hasn't worked). I actually learned of it from another post on the forum myself....
Click to expand...
Click to collapse
Exactly it has to differ some how so it would be nice to know in what way.
Anway as it has worked for all so far I am hoping to flash back tonight if I get the time and I will post my results after a few days to make sure the reboots have gone
Thanks again for your advice and help !
I performed the Nvflash to stock then rooted and used clockworkmod to install Revolver 3.11.1 and as before the ICS fiasco it looks to be resolved because my TF101 is still alive this morning no power off as it was doing before nvflash restore and no reboots at all.
I did notice that nvflash does create quite a few partitions and also does flash the HC bootloader so it has to be structure or bootloader that is the problem then because the kernel is taken out of the equation if I done a super wipe on my TF101 and installed HC with stock kernel.
On 22.4.2012 many people bricked their S2 while performing full wipe having Siyah kernel 3.1RC6.
What disappointed me is the update on development coming from developer in real hurry these days.
Developer need to test their development 1000 times before releasing it to users.
As a rule only we the user are responsible flashed kernel knowing the risk of RCs and BETAs.
We can't blame developer for this disaster.........
This thread is for those who bricked S2 and now are in process to recover their devices.
As a general habit, posts on bricked devices can be avoided easily by fan boys.
So now we need to help each other in the process of device recovery.
Please discuss here, what you are doing, any fix whether you found or not.
Thanks
Kachrukamble
kachrukamble said:
Yesterday many people bricked their S2 while performing full wipe having Siyah kernel 3.1RC6..
What disappointed me is the update on development coming from developer in real hurry these days.
Developer need to test their development 1000 times before releasing it to users
As a rule only we the user are responsible flashed kernel knowing the risk of RCs and BETAs.
We can't blame developer for this disaster, BUT.........
This thread is for those who bricked S2 and now are in process to recover their devices.
As a general habit, posts on bricked devices can be easily avoided by fan boys.
So now we need to help each other in the process of device recovery.
Please discuss here, what you are doing, any fix whether you found or not.
I will add Names for those who bricked S2 in OP
Thanks
Kachrukamble
Click to expand...
Click to collapse
Sad story bro. I know that feeling.
GM must be happy to hear that
Sent via my s2 monster
release candidate = not final = beta = not fully tested =still bugs = bricked = bug = because still beta= your own risk = your fault. Hope this helps.
Sent from my GT-I9100 using xda premium
Thanks for the info buddy. I'm in RC6 only. I was planning to do a full wipe and try out a ROM, and luckily I saw your post. Do let us know if you find a fix (for bricked phones). So can I just flash Siyah v3.1 and this problem will go away?
RobinRichard said:
Thanks for the info buddy. I'm in RC6 only. I was planning to do a full wipe and try out a ROM, and luckily I saw your post. Do let us know if you find a fix (for bricked phones). So can I just flash Siyah v3.1 and this problem will go away?
Click to expand...
Click to collapse
of course you can flash 3.1, it solves the issue. only the last updated rc6 had the problem. IF you are on rc6 better flash the updated kernel before doing any factory reset/data wipe to be in the safer side.
So did any one had a chance to solve it without going to service center??
bala_gamer said:
of course you can flash 3.1, it solves the issue. only the last updated rc6 had the problem. IF you are on rc6 better flash the updated kernel before doing any factory reset/data wipe to be in the safer side.
So did any one had a chance to solve it without going to service center??
Click to expand...
Click to collapse
What the hell happened? Efs cleared?
Gesendet von meinem GT-I9100 mit Tapatalk
I'm one of the "lucky" owners of a bricked-by-Siyah phone
I tried to flash a stock rom with odin but it doesn't work. I tried with:
- KI3, which is a 3-file-fw + .pit. The flash process hangs on data.img
- ILA2, which is a 1-file-fw. The flash with Odin is successful, but the phone can't boot and stays on the "Samsung Galaxy S2" screen all the time.
The only way to access recovery I found is to flash rogue recovery, but it can't mount internal sdcard so I can't flash anything
Ghost-of-the-Sun said:
I'm one of the "lucky" owners of a bricked-by-Siyah phone
I tried to flash a stock rom with odin but it doesn't work. I tried with:
- KI3, which is a 3-file-fw + .pit. The flash process hangs on data.img
- ILA2, which is a 1-file-fw. The flash with Odin is successful, but the phone can't boot and stays on the "Samsung Galaxy S2" screen all the time.
The only way to access recovery I found is to flash rogue recovery, but it can't mount internal sdcard so I can't flash anything
Click to expand...
Click to collapse
if you can access download mode, then you have many ways to recover your s2 without reaching SC
RobinRichard said:
Thanks for the info buddy. I'm in RC6 only. I was planning to do a full wipe and try out a ROM, and luckily I saw your post. Do let us know if you find a fix (for bricked phones). So can I just flash Siyah v3.1 and this problem will go away?
Click to expand...
Click to collapse
Happy to hear that you saved, many people didnt
Sent from my HTC EVO 3D X515m using Tapatalk
bala_gamer said:
if you can access download mode, then you have many ways to recover your s2 without reaching SC
Click to expand...
Click to collapse
Yes I can access it, but the internal sdcard is never mounted so I can't use my phone... I hope somebody will find and share a fix for this problem :-(
Unless the hardware is damaged, every full-bricked Galaxy S2 can be recovered witha J-tag repair.
If one does not have the hardware hardware to perform such a repair, he has to either purchase it or find somebody that has it nearby.
Ghost-of-the-Sun said:
Yes I can access it, but the internal sdcard is never mounted so I can't use my phone... I hope somebody will find and share a fix for this problem :-(
Click to expand...
Click to collapse
Did anyone try flashing a boot loader? Nothing to lose now really
Sent from my GT-I9100 using xda premium
Mine is bricked, partly due to me not reading the posts. I'm able to get into download mode, will have a play with Odin on the off chance something fixes it but I guess it's unlikely...
Ghost-of-the-Sun said:
Yes I can access it, but the internal sdcard is never mounted so I can't use my phone... I hope somebody will find and share a fix for this problem :-(
Click to expand...
Click to collapse
Try to enter 3e recovery and factory reset phone and see what happens mate. Wait for like 5 mins and if buttons light up ur good...
Gesendet von meinem GT-I9100 mit Tapatalk
Dang I'm on siyah rc6 still running, if I flash 3.1 or another kernel its safe right?
Its safe using cwm app
is CWM available at all on Siyah bricked mobiles?
bartoloandre98 said:
Dang I'm on siyah rc6 still running, if I flash 3.1 or another kernel its safe right?
Its safe using cwm app
Click to expand...
Click to collapse
flash immediately 3.1 without wipe
---------- Post added at 05:59 PM ---------- Previous post was at 05:56 PM ----------
itchetrigr said:
is CWM available at all on Siyah bricked mobiles?
Click to expand...
Click to collapse
its available but working with errors because of the mount problem of some partitions.
itchetrigr said:
is CWM available at all on Siyah bricked mobiles?
Click to expand...
Click to collapse
Bricked means dead in this case, you can't do anything with dead piece..
Well this just reinforces my belief to stick with stock kernels.
To the people with bricked phones, hope you guys are able to unbrick it without too much pain!
Does anyone know how to find a jtag service in korea, seoul? my phone is fully bricked and i need it back asap ....
Hi everyone. I know everyone is trying to get a fix on this exynos bug.. Me too. But it is also because of this bug that I was able to help root, flash cwm thru mobile Odin and follow up with custom rom for now 1x sgn2 and 4x sgs3 to custom rom DLL firmware. All this done out door on the go without any pc or computer... So it wasn't that bad a bug after all.:good:
kelvinator said:
Hi everyone. I know everyone is trying to get a fix on this exynos bug.. Me too. But it is also because of this bug that I was able to help root, flash cwm thru mobile Odin and follow up with custom rom for now 1x sgn2 and 4x sgs3 to custom rom DLL firmware. All this done out door on the go without any pc or computer... So it wasn't that bad a bug after all.:good:
Click to expand...
Click to collapse
I would like to see what would you write if your phone would be bricked and only samsung service center could repair........
I would rather be safe so I installed the new updates and a patched kernel (RedPill 1.01)
kelvinator said:
Hi everyone. I know everyone is trying to get a fix on this exynos bug.. Me too. But it is also because of this bug that I was able to help root, flash cwm thru mobile Odin and follow up with custom rom for now 1x sgn2 and 4x sgs3 to custom rom DLL firmware. All this done out door on the go without any pc or computer... So it wasn't that bad a bug after all.:good:
Click to expand...
Click to collapse
Its rare a bug like that works in our favor lol I wouldnt expect it to happen again for a fair while.
Goooooooooooooooooooood News...
Finally Found A Way To Unbrick The Tab, Which Requires Mainboard Replacement!
As You Know, If You Have Installed Wrong TWPR Recovery On 4.2 Update, And By Accident Have Erased Recovery Partition, Then You Would Have A HARD-Bricked Tab Which Showed: "Unrecoverable Bootloader Error"
In This State, Asus Support Center Required You To Pay (As You Are Unlocked) To Replace The Mainboard!!!
Finally, One Of Our Friends Found A Solution, Here Is The Link, I Just Wanted To Spread The Word...
It Saved My TF300T, Which Has Been Turned Off For 6 Months!
Here Is The Link, Just Be Patient And You Will Recover Your Tablet
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
wow man if this is true I'll unlock my bootloader and flash a custom rom even today!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4
it could easily recover my tab, which was supposed to be sent to Asus next week
it's a milestone, greatly helped...
wow. my post seemed to be the phoenix essence for al lot of tabs (without the need to burn something down)
After Reading it again - my solution is not only for a bad recovery partition - its for any PIT related errors (bad flash - which was my case) etc.
cheers and GL
-Buster
Sent from my GT-I9505 using xda app-developers app
Buster99 said:
wow. my post seemed to be the phoenix essence for al lot of tabs (without the need to burn something down)
After Reading it again - my solution is not only for a bad recovery partition - its for any PIT related errors (bad flash - which was my case) etc.
cheers and GL
-Buster
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
you saved hundreds of dollars for us, i wish i could donate
i just can say: "I DO APPRECIATE" <3
thanks more than a million, bro
Best fix ever.
Thanks !
:good::good:
therock3181 said:
Best fix ever.
Thanks !
:good::good:
Click to expand...
Click to collapse
press "Thanks" button if it helped
this! a thousand times this!
i'm hitting the thanks button like its going out of style, will see about donating as you just saved my brick from 5 months of staying in a cabinet!
this needs to be sticked, or the original post! holy crap i am happy
This is how i unbricked mine. Try it.
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!
How to uninstall or remove TWRP recovery from tf300?
If this works ... picture this ... ASUS is a rubish tab ... it's totally broken ... i'm lucky if my finger causes the right movements to happen ... so yeah it gets picked up tomorrow .. and without this i'm gonna have to PAY for it to be picked up haha
so lets hope i can stay up all night now and try it out .... literally i didn't find this answer for a year ... why can't i search it ...
How to uninstall or remove TWRP recovery from tf300?
Go back to stock rom tf300
willl report back with love iif it works haha
FAIL ... i thought this was for people who got locked into a bad version of TWRP ... i guess not .. still uses fastboot ... major fail
Thanks you just save my tf
interslicer said:
If this works ... picture this ... ASUS is a rubish tab ... it's totally broken ... i'm lucky if my finger causes the right movements to happen ... so yeah it gets picked up tomorrow .. and without this i'm gonna have to PAY for it to be picked up haha
so lets hope i can stay up all night now and try it out .... literally i didn't find this answer for a year ... why can't i search it ...
How to uninstall or remove TWRP recovery from tf300?
Go back to stock rom tf300
willl report back with love iif it works haha
FAIL ... i thought this was for people who got locked into a bad version of TWRP ... i guess not .. still uses fastboot ... major fail
Click to expand...
Click to collapse
wrong recovery can always be flashed with another one if fastboot works.
if only recovery is your problem no need to go back to stock. but on most cases it's the best way to get a clean start.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
wrong recovery can always be flashed with another one if fastboot works.
if only recovery is your problem no need to go back to stock. but on most cases it's the best way to get a clean start.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
what if you can't get into recovery and only APX?
I tried installing CWM (for CM11) over an 2.6.0.0 TWRP (4.2) with 10.6.15.3 and no go!
I'm stuck with APX only.
Any ideas? I've tried NVFLASH but can't fix 64bit drivers that work properly. Naked 0.73 didn't either. I can only get the Asus Transformer Prime APX to work properly.
snoopspecial said:
what if you can't get into recovery and only APX?
I tried installing CWM (for CM11) over an 2.6.0.0 TWRP (4.2) with 10.6.15.3 and no go!
I'm stuck with APX only.
Any ideas? I've tried NVFLASH but can't fix 64bit drivers that work properly. Naked 0.73 didn't either. I can only get the Asus Transformer Prime APX to work properly.
Click to expand...
Click to collapse
are you sure its apx?
also for cm11 based roms for the tf300t you need a special recovery (check the omnirom thread - thats the one im using, scannos twrp 2.6.3.0)
you cant run cm11 with older recovs since the PITs changed apparently (haven't read the man pages yet) but thats what i understood out of the omni thread
nvfalsh only works if you backed up your device prior bricking.
cheers & gl
Buster
Buster99 said:
are you sure its apx?
also for cm11 based roms for the tf300t you need a special recovery (check the omnirom thread - thats the one im using, scannos twrp 2.6.3.0)
you cant run cm11 with older recovs since the PITs changed apparently (haven't read the man pages yet) but thats what i understood out of the omni thread
nvfalsh only works if you backed up your device prior bricking.
cheers & gl
Buster
Click to expand...
Click to collapse
So it is a really good idea to backup your device prior to bricking it , to backup your device, use flatline (google it. sorry for not providing the link, this forum does not allow me to post links yet)
Buster99 said:
are you sure its apx?
also for cm11 based roms for the tf300t you need a special recovery (check the omnirom thread - thats the one im using, scannos twrp 2.6.3.0)
you cant run cm11 with older recovs since the PITs changed apparently (haven't read the man pages yet) but thats what i understood out of the omni thread
nvfalsh only works if you backed up your device prior bricking.
cheers & gl
Buster
Click to expand...
Click to collapse
As far as I can tell Vol+ gets me the black screen and recognized as a device in Windows 7 x64 as an ASUS APX Interface. I tried replacing the driver with every combination of NVIDIA, Google, Android SDK, Naked .72/.73 and no go. I've also tried ADB drivers and no luck there either.
Vol- doesn't bring up anything - screen just stays at ASUS logo. I dont get the recovery menu and can't get into TWRP (original) or CWM (after attempting to install). My mistake for not just sticking with TWRP (previously on 2.6.0.0) and using the scannos version.
It basically gets to the Device is Unlock, ASUS and NVIDIA logo and doesn't proceed further.
Any ideas?
Thanks in advance.
with the logos are there also 3(or 4) icons?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
with the logos are there also 3(or 4) icons?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
neither - i dont ever get to that.
Same here - stuck at the first ASUS logo - in the left corner "the device is unlocked" and right corner the Nvidia logo.
Vol+ and power or Vol- and power - no effect.
I flashed an old recovery using adb commands in a newer twrp so is there any way to fix this?????
Sent from my LG-E980 using Tapatalk
I flashed the Lollipop firmware on my note 4 (910G) and badly wanted to root. In the process of rooting i may have used the wrong CWM file. But i checked it doesnt seems so but i assume. Im not sure. Im not a noob (but not an expert) as i tinkered many phones so many times. But today things went wrong for the 1st time.
The issue is the calibration of the digitizer on my Note 4, its completely off, in some areas it doesnt work at all when using my fingers, but with the S-Pen it seems fine. Its impossible to use the phone, the gap is huge.
I re-installed the stock firmware it doesnt seems to install the stock recovery (Assuming its the recovery i flashed which caused this) hence didnt rectify.
I flashed the philz and twrp recoveries (Correct files) thinking having a working recovery would solve and that too did not help.
I flashed CM based ROM assuming it would make a difference, still no.
Please guys help fix this, and i really really hope its not hardware or triggered any chips to malfunction due to incorrect file flash. Pls help and advice what needs to be done to reverse this.
Thank you...
Flashing official stock firmware should revert your recovery back to standard. It did for me when I was using Cwm and reflashed 5.0.1 firmware.
try your device in safe mode to see if that changes anything. If not I'd recommend doing a complete wipe then reflashing the stock firmware.
BNerd89 said:
Flashing official stock firmware should revert your recovery back to standard. It did for me when I was using Cwm and reflashed 5.0.1 firmware.
try your device in safe mode to see if that changes anything. If not I'd recommend doing a complete wipe then reflashing the stock firmware.
Click to expand...
Click to collapse
No mate tried all that, makes no difference. Even in safe mode its still behaves the same. And installed stock firmware many times, also without battery too. No improvement. Even the stock recovery isn't installed, thats the biggest question i have in that process.
malakalofung said:
I flashed the Lollipop firmware on my note 4 (910G) and badly wanted to root. In the process of rooting i may have used the wrong CWM file. But i checked it doesnt seems so but i assume. Im not sure. Im not a noob (but not an expert) as i tinkered many phones so many times. But today things went wrong for the 1st time.
The issue is the calibration of the digitizer on my Note 4, its completely off, in some areas it doesnt work at all when using my fingers, but with the S-Pen it seems fine. Its impossible to use the phone, the gap is huge.
I re-installed the stock firmware it doesnt seems to install the stock recovery (Assuming its the recovery i flashed which caused this) hence didnt rectify.
I flashed the philz and twrp recoveries (Correct files) thinking having a working recovery would solve and that too did not help.
I flashed CM based ROM assuming it would make a difference, still no.
Please guys help fix this, and i really really hope its not hardware or triggered any chips to malfunction due to incorrect file flash. Pls help and advice what needs to be done to reverse this.
Thank you...
Click to expand...
Click to collapse
Have you tried to update the firmware of the touchscreen? Enter *#2663# into the dialer with your S pen and then click TSP FW Update.
Oh my God. Bro u saved my life. Thank you so much for replying and suggesting this. U r post was the 1st thing I read and did and it worked. Thanks man. Thanks so very much. U don't know how delighted I am now. Thank you again.....
Sent from my SM-N910G using XDA Free mobile app
Hmm.. Wonder why this issue occurred in the first place... I doubt it's due to rooting, though..
Sent from my SM-N910G using Tapatalk
coolfire said:
Hmm.. Wonder why this issue occurred in the first place... I doubt it's due to rooting, though..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Well im sure i followed the process right but now i doubt it used an incorrect file (CWM) to flash on odin, which caused this. Anyhow thank God its fine now lol. I Was literally in tears man. Ha ha
I can totally understand how you felt. Glad all is great now!
Sent from my SM-N910G using Tapatalk
This problem has nothing to do with rooting or installing a custom recovery. Only when upgrading or downgrading firmwares the touchscreen firmware can sometimes bypass the update.
Good one... Hackberrybold