Related
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
garaxiel said:
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
Click to expand...
Click to collapse
You're problem is ClockworkMod. Version 5 is a steaming heap of crap that's caused this sort of problem, not only for dInc users, but Tbolt and other device users. The solution seems to be flashing back to an older recovery. And if it works, don't fix. I'm still running version 3.something on my Tbolt and have no plans to change that. I NEVER use ROM Manager and recommend nobody ever touch it except for a few things. I almost never have it installed on any device.
OK then dumb question but if RomManager FC's on me, how do i flash back to a working version or to an alternate version entirely? i have been unable to find other ways of flashing outside of RomManager
Older Recovery versions are available on "dougpiston.com" just follow the directions.
www.dougpiston.com has what you're looking for under "recoveries". They're flashed in hboot like a radio, RUU, splash screen, etc.
Also if that doesn't work, which it probably will, you can also flash a PB31IMG which essentially is the RUU but you do not need a PC. You put that on the root of the SD (as in, not in any folders. Probably know that already...) and reboot into HBOOT (Power and volume down) and itll load it up.
Note: Make sure the file is PB31IMG.zip and not PB31IMG.zip.zip
Ha!!! got it back (well on the road to back anyways)
Was able to find a PB31IMG on dougpiston.com and hboot flashed it in (3.0.0.8). I had one on my PC but it must have been corrupt because it didn't work before. once that was working i was able to get into recovery get a restore back to my 175 nightly and am in the process now of flashing nightly 181 on there cleanly and rebuild the whole phone from scratch. damn i hope this works thanks all for help and ideas.
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
pete_kowalski83 said:
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
No idea...are you using ROM Manager?
What's up guys!
Using ROM installer I flashed vanir 4.4 along with 4.4 gapps on my sprint gs3 sph l710. I wiped the cache and it looked as if it were installing fine but winded up getting stuck in boot loop mode instead. Now when I try to boot into recovery the twrp screen flashes and then it goes straight into bootlop mode from there. Now i cant acsess any of my backups. I can get into down load mode but unfortunately my computers messed up right now. I can't hit the run button on Odin because the screen is too big. I know it sucks!!! Does anyone know some tricks I can use or have any recommendations. Your help would be greatly appreciated! BTW.. I was running illusion 4.3 when this happened.
ddray said:
What's up guys!
Using ROM installer I flashed vanir 4.4 along with 4.4 gapps on my sprint gs3 sph l710. I wiped the cache and it looked as if it were installing fine but winded up getting stuck in boot loop mode instead. Now when I try to boot into recovery the twrp screen flashes and then it goes straight into bootlop mode from there. Now i cant acsess any of my backups. I can get into down load mode but unfortunately my computers messed up right now. I can't hit the run button on Odin because the screen is too big. I know it sucks!!! Does anyone know some tricks I can use or have any recommendations. Your help would be greatly appreciated! BTW.. I was running illusion 4.3 when this happened.
Click to expand...
Click to collapse
Can you try using this? http://forum.xda-developers.com/showthread.php?t=1746680
Maybe that'll work, you can use it to return to stock, and if anything I would recommend going back to stock before doing anything else. Also, it may not be the consensus of the site here but in my own opinion, I don't like using rom installer or goo manager or anything. I like doing it all myself in recovery. I've heard one too many stories of people getting hardbricked because their rom installer or whatever downloaded the international version of the rom they wanted :/ always best to check your own md5 checksums and make sure you're downloading the rom for your phone from your phone's forum.
As for the exact reason your phone did that? I couldn't tell you, maybe with a little more info someone more knowledgeable here could tell you
So i got my computer fixed. I havent tried the tool kit in the thread you recommeded. I decided first to use a stock file i have on odin first that has saved me from softbricks in the past. I set everything up hit start, watched the process complete with the pass. Now it shows the stock boot animation but still stuck in bootloop mode. I put it into recovery,which is now stock instead of twrp, wiped cache, davlik cache and factory reset then i reconnected to odin and reflashed the stock file. Still stuck in bootloop mode!!!! Plain reboot and same thing :/ so for the hell of it, i wanted to see if i can to my backups by restoring twrp. So i flashed my cf auto root and then flashed my twrp file and bam!!!! Twrp was full functioning with all my backups!!! :laugh: next i restored my latest illusion 4.3 rom and wala! Ive got a fully functioning rooted phone with a custom rom. I flipped through everything to make sure it looks good and it does. Except.... any photos and music that are saved to phone and not sd card are gone I dont understand, everthing else is backed. Contacts, call logs, messages, text messages, apps, customised settings etc...I even flashed my carbon rom that had the same music and pics. When i open gallery it shows the photo count in snapseed and others im looking for but then they all start dissapearing!!! i also dont understand why the stock file which has saved me from softbricks before didnt work. I dont know anything about checking md 5 checksums but if its worth the time ill do my research! Im happy i got my phone working but i would like to be more solid in what im doing. Maybe someone can help shed some light on this.
I have a specific problem .. I think in order for anyone to understand it, I have to explain it well.
I was flashing the new LegacyXperia ROM on my Xperia Arc S (http://forum.xda-developers.com/showthread.php?t=2545354) .. before, I had an older version of LegacyXperia already installed, with CM10.2.
Anyhow, I forgot to flash the boot.img! I did everything else as I should and istalled the ROM. Yet now when rebooting the phone from recovery, it only gets to the "LegacyXperia" screen (I don't know how this is officially called .. it's the first screen you see) and not further. Well, if I press the home button when it's starting, I get to recovery mode. .. So I've been trying my best to fix this. This includes:
Currently I have another Arc S device to work with - I have made a backup through recovery on that device (which works perfectly, running a different ROM) and tried to run it on the "broken" device .. recovery said it went well, but when starting the phone, nothing changed.
I've tried installing a different ROM (the one that is also installed on the second device), but again nothing changed.
I've tried wiping pretty much everything but the "dalvik cache" (since I don't know what this particular cache is) and installing the different rom and/or using the backup. Nothing made a difference.
I've even made an attempt on install the forgotten boot.img - I've taken the previously mentioned backup, put the boot.img into it (all that was on the SD card, via my computer, of course), and added the md5 values to the md5 file. Well, my phone was giving me a md5 mismatch, so I tried wiping everything off the md5 file, which seemed to do the trick (this is a useful thing to know!), since I was able to go through with the process of recovering the boot.img through recovery. After I've managed that, I've reinstalled the LegacyXperia ROM as I should have in the beginning. Yet again, nothing changed! the phone still won't start!
I am really desperate and out of ideas. ..the only idea I have left is try to install an older version of legacyxperia (the one I probably had before) .. but since installing a completely different ROM didn't work, I have only little hope..
I was not able to get into fastboot .. I do not know if it's enabled or not, since it was not me who installed the previous ROM on my phone. I know, shame on me ..
I hope I wrote down everything one could need in order to help me. And please do help me, I ran out of ideas and would REALLY hate to loose this phone!
I didn't understand the part of adding MD5 values to the MD5 file, but whatever
I don't really see why the rom wouldn't boot up, unless the kernel just isn't being flashed. (Maybe the previous owner relocked the bootloader?)
Can't you fastboot the kernel?
Also, Dalvik Cache can and actually should be wiped when installing a new rom.
SOLVED
Yeah, I got the feeling the kernel didn't flash, too! .. perhaps the bootloader was re-locked, but I really don't see why one would be doing that..
I was trying to get to the fastboot screen (with all the button-pressing and usb-plugging), but didn't manage that. However, I found a solution! (and god bless the guy who put this up!) I followed this thread [it seems xda-developers won't let me post an outside link .. anyhow, it's a thread on androidgadgematic.com, titled "How To Fix Bricked Sony Xperia Android Phone With Flashtool [ Unbrick ]" from june 17, 2012] and managed to install the stock ROM without much trouble. Now the phone is again running nicely I did, however, have to get a seperate driver package, since the one supplied with the flashtool wouldn't instal - I googled the drivers and used version 1.5 from xda-developers' forum.
GOSH I'm glad this is over
So like the title says, I flashed the wrong recovery version - specifically, the Note 4 Edge - on accident. The touch screen is all sorts of funky now, the top left is accurate but if I want to click something lower on the screen I have to touch about an inch above it. The S-Pen works fine - still as precise as ever. I have so far attempted to flash the correct recovery, Odin to NK2 twice, wiped, uberwipe.zip, restored from nandroid. Nothing has worked. Anyone know where the touch screen data is stored and how to reset it? I can navigate the phone with the S-pen to try any solutions, as well as ADB.
Thanks!
We had another user do something similar but hasn't been replying to help responses. The issues may continue to be unresolved for him. If you find a solution, shoot him a PM. In the meantime, try some of things he tried or was suggested by following his posts or quotes.
I think this was my last reply to call for help:
http://forum.xda-developers.com/showthread.php?p=61903464
Did you try to restore your last nandroid and Odin just the stock recovery of the build that it came from? If you've been on a OE1 or OF5 build and don't have a nandroid, I'd be careful of trying to go back with a nandroid or Odin or ROM zip. That causes more trouble than it's worth.
I found a solution actually! Dial *#2663# (using S-pen in my case, since it works still), then update the touch FW by pressing "TSP FW update (General)"
Credit for the solution goes to tat2me2, I'm just posting it here for others. I'll try to find the other guy and shoot him a PM as well if someone else doesn't already.
Thanks!
Edit: I followed your link AFTER my post, sorry - same solution there. Perfect!
*#2663# OK
Delete
So your touchscreen is back to normal now? Did you find a stable ROM and recovery?
Hello Everybody
I hope you can help me with my first Androidproblem.
I installed rootprivileg on my Tab by flashing Custom-Rom with Odin etc.
Everything was working fine after that. Super-SU was working and i was root and was able to change CPU-Settings and everything else. Now my problem. Since i am a Technerd and always want to learn more, i wanted to restore the system to default to have a clean device. I made a backup with Kies which worked fine (Windows 10). Then i went to the Settings menu on my tab and choose the reset option. Than the screen went black. Since then Android is only booting into CWM-Mode and the Tablet is not recognized anymore by Kies when i connect it via USB-Cable. It is recognized as a USB-Device by Windows but i cant restore the backup on the tablet.
When i press the powerbutton the tab always reboots in CWM-Recovery v. 6.0.4.8.
What can i do to solve the problem? Thank you very much for your help.
I really need it.
Naturestone said:
Hello Everybody
I hope you can help me with my first Androidproblem.
I installed rootprivileg on my Tab by flashing Custom-Rom with Odin etc.
Everything was working fine after that. Super-SU was working and i was root and was able to change CPU-Settings and everything else. Now my problem. Since i am a Technerd and always want to learn more, i wanted to restore the system to default to have a clean device. I made a backup with Kies which worked fine (Windows 10). Then i went to the Settings menu on my tab and choose the reset option. Than the screen went black. Since then Android is only booting into CWM-Mode and the Tablet is not recognized anymore by Kies when i connect it via USB-Cable. It is recognized as a USB-Device by Windows but i cant restore the backup on the tablet.
When i press the powerbutton the tab always reboots in CWM-Recovery v. 6.0.4.8.
What can i do to solve the problem? Thank you very much for your help.
I really need it.
Click to expand...
Click to collapse
Read the last post of the CWM thread.
Sent from my SM-G920V using Tapatalk
Could you please sent me a link to the CWM-Thread, so that i know with thread you mean? That would be very friendly.
I think i got the idea for solving the problem, but after reading for 8 hours on xda i feel like i am blind. So many different roms....so many ways to handle it. I am confused.
I would like to install the Una T111-Rom which also seems to work with the T110 Tab. But there is a big problem: Since i dont have access to my sd-card anymore i cant copy the rom in the backup-folder on the sd. I could take the sd-card out of the tab if i would find the adapter to the bigger format SD-Card, then i could put the card in my notebook and copy the file in the right directory. Maybe it would work then and i have a nice safe googlefree Tab.
Thank you very much for your kindness
Maybe using Adb is an option?:fingers-crossed::
I hope i have a solution now. I will try to install the Criskelo-Rom (although i am not a big fan of the dark colors in there) with Odin. I hope it works....because its starting to get intense....for a newbie like me.
Hello everybody
After having a constant bootloop in the CWM-Recovery i now managed to flash TWRP v.2.7.0.1 and it works. At least i boot into TWRP instead of CWM now. Its the TWRP-Version of SELinux and i cant access the kernels content, it says. What would be the next step? I can access my data on the (wiped) sd and main partition now but i still dont have the possibility to install the rom i would like (Criskelo or Stock NE4lite for T110) because i cant get it on the sdcard. I would really like to get back in the Androidbootup of my Tab...
Please help me out. I really need your experience with this. It took me 24 hours and a lot of reading, downloading etc to get to this point.
Thank you very much.
Very beautiful TWRP-Interface bye the way. Very impressive.
It says: Kernel does not have support for reading SELinux contents.
Hello guys
Keeping you up to date. I am smarter now...
I flashed the device with this custom-rom: T110UEUANE4. I transferred this file to my sdcard using ADB and then installed the Rom. Worked perfect.
Great Tutorial: https://www.youtube.com/watch?v=VTGIAzofZCM
After rebooting i was hoping it would boot into Android, but it didnt. It booted into the TWRP and the screen flickered.
So i flashed again with this one: Philz Touch Advanced CWM recovery
Here i had the problem that ADB didnt work, so i flashed back the TWRP 2.7.0.1
I would like to know why i cant boot into Android after i installed the Custom-Rom for T110.
Any help and suggestions are deeply appreciated cause i am learning fast but i am still learning.
Bye the way: Now i understand how you can get addicted to flashing. But it would be nice to be able to boot in the system again...
Many thanks for your help.
Naturestone said:
Hello guys
Keeping you up to date. I am smarter now...
I flashed the device with this custom-rom: T110UEUANE4. I transferred this file to my sdcard using ADB and then installed the Rom. Worked perfect.
Great Tutorial: https://www.youtube.com/watch?v=VTGIAzofZCM
After rebooting i was hoping it would boot into Android, but it didnt. It booted into the TWRP and the screen flickered.
So i flashed again with this one: Philz Touch Advanced CWM recovery
Here i had the problem that ADB didnt work, so i flashed back the TWRP 2.7.0.1
I would like to know why i cant boot into Android after i installed the Custom-Rom for T110.
Any help and suggestions are deeply appreciated cause i am learning fast but i am still learning.
Bye the way: Now i understand how you can get addicted to flashing. But it would be nice to be able to boot in the system again...
Many thanks for your help.
Click to expand...
Click to collapse
You need to install stock recovery. Then reboot. The first reboot will boot into recovery, then you should be able to boot into rom.
Sent from my SM-T310 using Tapatalk
Hello Everybody
I flashed my Tab successfully now with the custom-rom from mknrls. Many thanks for your work and your passion.:good:
Also i want to thank gr8nole for the keyword: Stock Recovery. Thanks for your files and your help.
The Tab is running well, except for the issue with the contacts - which is not such a big deal cause i use my Nokia N9 as a phone...not only as a phone... After flashing, it took me several days to "recover" myself from the loss of sleep.
I flashed the Tab 4 days ago.
My next Custom-Androidrom will probably be on my beloved N9.:good:
Maybe i will try to install UNA-OS on my Tab...i think i am becoming flash-addicted.
Sent from my SM-T310 using Tapatalk[/QUOTE]