Related
Hy everybody,
I have got a big problem with my i9000: it doesn't start up very properly i mean it takes a lot to start the S logo animation, the animation is very slow (really low fps) and it usually stuck at the end of the animation (only once i managed to arrive to the menu where you have to choose the language but the touchscreen was not responding). Even CWM recovery is slow! There is a lag while choosing the options. I also tried to reflash using stock Samsung ROMS such as XXJPU and XXJW7 but i get the same issue. Also tried to install custom ROM via CWM, i get the speed back but touch doesn't work! I have already searched on the site for this issue and got a thread that had exactly the same problem but didn't manged to get out from this situation (here is the thread http://forum.xda-developers.com/showthread.php?t=1422634, it's exactly the same issue!).
I have been flashing and repearing android devices for years and this is the first time i meet this kind of issue! Maybe it is a bootloader problem or motherboard, but i ask you experts before getting in troubles =)
Sorry for my bad english :victory:
Cheers :laugh:
I think it is a hardware problem mate(since you flashed too many roms...)
Rooting wont help you too so...
Even if you dont have warranty give it for repairing..
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
Uhm i don t have warranty anymore but i'm able to disassembly and replace any piece i need. Hope it is not a motherboard prolem, but i can t image something different...
NotoriuStyle™ said:
Uhm i don t have warranty anymore but i'm able to disassembly and replace any piece i need. Hope it is not a motherboard prolem, but i can t image something different...
Click to expand...
Click to collapse
First pull out everything, Ext SD card, Sim Card, power up after a few min of pressing power button..get into CWM recovery and format SD card, everything and wipe... flash a rescue kit from My Android Collection, link below
If you cannot format Internal SD card in recovery use a Format tool from My Android collections link below to format it from PC
xsenman said:
First pull out everything, Ext SD card, Sim Card, power up after a few min of pressing power button..get into CWM recovery and format SD card, everything and wipe... flash a rescue kit from My Android Collection, link below
If you cannot format Internal SD card in recovery use a Format tool from My Android collections link below to format it from PC
Click to expand...
Click to collapse
When you say format everything do you mean format /boot too ? Thank u for your help =]
NotoriuStyle™ said:
When you say format everything do you mean format /boot too ? Thank u for your help =]
Click to expand...
Click to collapse
can be done, but If you don't have boot loader on the ROM , you will have problem, so avoid it , for now
xsenman said:
First pull out everything, Ext SD card, Sim Card, power up after a few min of pressing power button..get into CWM recovery and format SD card, everything and wipe... flash a rescue kit from My Android Collection, link below
If you cannot format Internal SD card in recovery use a Format tool from My Android collections link below to format it from PC
Click to expand...
Click to collapse
I did everything and than flashed "i9000 Rescue Darky's ROM Resurrection edition" but with no result, even the robotic voice of Darky's ROM is laggy!! Trying other rescue kit and will let you know
NotoriuStyle™ said:
I did everything and than flashed "i9000 Rescue Darky's ROM Resurrection edition" but with no result, even the robotic voice of Darky's ROM is laggy!! Trying other rescue kit and will let you know
Click to expand...
Click to collapse
remember to do full wipes /factory reset before and after flashing the ROM and Internal SD card must be formatted
xsenman said:
remember to do full wipes /factory reset before and after flashing the ROM and Internal SD card must be formatted
Click to expand...
Click to collapse
Yes i always wipe data, wipe cache, wipe dalvik and wipe battery stats. Tried even GB Flash Kit and Rescue Kit for i9000 using heimdall packed but nothing. Boot animation is always slow and after 1 hour, after getting loaded, touch doesn't work =(
Nothing ... tried everything excpet formatting /boot. Will i risk to brick my device if i choose that option ?
NotoriuStyle™ said:
Nothing ... tried everything excpet formatting /boot. Will i risk to brick my device if i choose that option ?
Click to expand...
Click to collapse
Nope, but you must not try to reboot after formatting it, . You need to power down, do a battery pull and flash a ROM package with boot loader for phone to function
xsenman said:
Nope, but you must not try to reboot after formatting it, . You need to power down, do a battery pull and flash a ROM package with boot loader for phone to function
Click to expand...
Click to collapse
I've done 3 wipes then the 5 formats (boot too) then while still in recovery flash Elite's JB RC 12.1 rom .. if problems then it's deff a hardware issue
Sent from my GT-I9300 using xda premium
jj92942000 said:
I've done 3 wipes then the 5 formats (boot too) then while still in recovery flash Elite's JB RC 12.1 rom .. if problems then it's deff a hardware issue
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Nothing =( every rom i flash via CWM gives speed back but touch doesn't work =S
NotoriuStyle™ said:
Nothing =( every rom i flash via CWM gives speed back but touch doesn't work =S
Click to expand...
Click to collapse
Then it's hardware .. any gb rom gives you touch?
Sent from my GT-I9300 using xda premium
jj92942000 said:
Then it's hardware .. any gb rom gives you touch?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Uhm every rom i tried via CWM, and even the stock rom when it gets loaded, doesn't give me a working touchscreen. This problem happened last month too and after flashing a lot of roms i managed to solve it in the end, but i was just lucky because i didn't know what the device had and i solved just flashing random ROMS and getting solved with XXJW7. That's why i'm not so sure it is a hardware problem =(
NotoriuStyle™ said:
Uhm every rom i tried via CWM, and even the stock rom when it gets loaded, doesn't give me a working touchscreen. This problem happened last month too and after flashing a lot of roms i managed to solve it in the end, but i was just lucky because i didn't know what the device had and i solved just flashing random ROMS and getting solved with XXJW7. That's why i'm not so sure it is a hardware problem =(
Click to expand...
Click to collapse
Try Elite JB RC12.1, if working on jw7, do a android backup, then you'll have to flash JVU 1st, if touch screen works then it'll work with the JB rom, here's a trick, instructions are there but do this. Backup everything to pc, take out sdcard, before flash jvu, do 3 wipes, data, cache, dalvik, then go to usb mount, format 5 items there, boot, data, cache, system, sdcard ( last wipes everything). Now do 3 wipes again, yes again, flash JVU, root, transfer Rom to sdcard, 3 wipes, do usb mount, then 4 formats (not sdcard), 3 wipes again, flash JB rom. If bootloop, no bigger it just flashed kernel, take battery out, wait back in recovery flash Rom. You'll be on JB.
Sent from my GT-I9300 using xda premium
dreamer94 said:
I think it is a hardware problem mate(since you flashed too many roms...)
Rooting wont help you too so...
Even if you dont have warranty give it for repairing..
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
Flashing your phone multiple times, does not make it slow. I have flash my phone almost every day, to check out new roms that are released every day and my phone hasn't slowed down a bit
---------- Post added at 04:16 PM ---------- Previous post was at 04:10 PM ----------
NotoriuStyle™ said:
Hy everybody,
I have got a big problem with my i9000: it doesn't start up very properly i mean it takes a lot to start the S logo animation, the animation is very slow (really low fps) and it usually stuck at the end of the animation (only once i managed to arrive to the menu where you have to choose the language but the touchscreen was not responding). Even CWM recovery is slow! There is a lag while choosing the options. I also tried to reflash using stock Samsung ROMS such as XXJPU and XXJW7 but i get the same issue. Also tried to install custom ROM via CWM, i get the speed back but touch doesn't work! I have already searched on the site for this issue and got a thread that had exactly the same problem but didn't manged to get out from this situation (here is the thread http://forum.xda-developers.com/showthread.php?t=1422634, it's exactly the same issue!).
I have been flashing and repearing android devices for years and this is the first time i meet this kind of issue! Maybe it is a bootloader problem or motherboard, but i ask you experts before getting in troubles =)
Sorry for my bad english :victory:
Cheers :laugh:
Click to expand...
Click to collapse
Why dont you try flashing your original firmware via Odin with "repartition" ticked. Once that is done, let your phone boot and see if there's and lag. If lag still persists, go to CMW, format system, boot and data and restart your phone and then check again
Touchscreen problem
NotoriuStyle™ said:
Hy everybody,
I have got a big problem with my i9000: it doesn't start up very properly i mean it takes a lot to start the S logo animation, the animation is very slow (really low fps) and it usually stuck at the end of the animation (only once i managed to arrive to the menu where you have to choose the language but the touchscreen was not responding). Even CWM recovery is slow! There is a lag while choosing the options. I also tried to reflash using stock Samsung ROMS such as XXJPU and XXJW7 but i get the same issue. Also tried to install custom ROM via CWM, i get the speed back but touch doesn't work! I have already searched on the site for this issue and got a thread that had exactly the same problem but didn't manged to get out from this situation (here is the thread http://forum.xda-developers.com/showthread.php?t=1422634, it's exactly the same issue!).
I have been flashing and repearing android devices for years and this is the first time i meet this kind of issue! Maybe it is a bootloader problem or motherboard, but i ask you experts before getting in troubles =)
Sorry for my bad english :victory:
Cheers :laugh:
Click to expand...
Click to collapse
Hey!! I tried various ROM combinations and it worked for a few months. Although even after a few days, the problem would reappear and I was forced to flash again(it started working after flashing about 30-50 ROMs). Finally, a month back, I came across the same problem again but this time, nothing worked. After hitting my head on the wall for a month, I finally gave it to the Samsung ppl and they figured that the problem was with the touchscreen!!(zoinks!!) They will replace the touchscreen and it would cost me $145(8,000INR , expired warranty). They'll return it in 4 days. I'll post more when I get my SGS back.
Hmm, looks to me, you must have flashed something wrong/flashing process goes wrong. I would suggest this 'solution':
1. Flash a new recovery system. I suggest the latest TWRP recovery or flash the latest CWM. To me, CWM has given me lots of problems. You can flash it through computer or through CWM using their flashable zip.
2. Once then, wipe everything! Data, cache, dalvik cache.
3. Next, format the system! If you formatted system, you will lose your current rom. Meaning the phone will not boot up until you install/flash a ROM.
4.Install necessary stuff like Google Apps
Done! Things should be working right now. I had problems like you, my phone sometimes takes 2-5 minutes to boot.
I'm using the Samsung Galaxy S Plus I9001. So, I flashed Acro86's ICS rom. Super smooth.
Hope I helped you!
Sent from my GT-I9001 using xda app-developers app
Hi, I have exactly the same problems.
I guess it's also touch error, I already changed it once and after the year and then started having problems as it was pressed alone, stuck all the time and stopped working. As I was reading and testing, I think I'll buy again the touch.
From Argentina.
Regards.
Hey guys,
New to Xperia SP modding, just rooted my phone following the instructions on the forums, unlocked my bootloader and flashed CWM recovery.
Since then I have tried to access my storage through PC to drop in some ROMS, and I get 'Error: device has been removed' messages.
It allows me to copy from the device but not to it.
If I change the storage method to MSC I can copy to external storage but CWM calls the ROM's bad files.
I have tried fix permissions, wipe dalvik and a full factory reset. No luck whatsoever.
Anyone offer any advice please?
blackassassinuk said:
Hey guys,
New to Xperia SP modding, just rooted my phone following the instructions on the forums, unlocked my bootloader and flashed CWM recovery.
Since then I have tried to access my storage through PC to drop in some ROMS, and I get 'Error: device has been removed' messages.
It allows me to copy from the device but not to it.
If I change the storage method to MSC I can copy to external storage but CWM calls the ROM's bad files.
I have tried fix permissions, wipe dalvik and a full factory reset. No luck whatsoever.
Anyone offer any advice please?
Click to expand...
Click to collapse
have you tried using different usb ports on your computer? check the size of the rom file, if its below 500 mb the download was probably corrupt.
Start again. Flash a stock ROM using flash tools, flash a kernel tha already has CWM in it and auto roots - check everything works.
Sounds like something has gone wrong along the way - someone may be able to help, but rather than waiting for an answer, it's sometimes best/quicker to do all the steps again. Unless your phone has faulty hardware, the vast majority of problems can be solved this way.
Parkside said:
Start again. Flash a stock ROM using flash tools, flash a kernel tha already has CWM in it and auto roots - check everything works.
Sounds like something has gone wrong along the way - someone may be able to help, but rather than waiting for an answer, it's sometimes best/quicker to do all the steps again. Unless your phone has faulty hardware, the vast majority of problems can be solved this way.
Click to expand...
Click to collapse
For this to do your bootloader need to be unlocked if im not mistaken
mrjraider said:
For this to do your bootloader need to be unlocked if im not mistaken
Click to expand...
Click to collapse
He says he has unlocked his bootloader...
Parkside said:
He says he has unlocked his bootloader...
Click to expand...
Click to collapse
Whoops.. My bad... Did not read properly
FlashTool
Have you use FlashTOOl to put the original software on your phome
Fixed this eventually something had gone wrong with the rom I was on. I ended up reflashing a different kernel via flashtool and it worked to flash another rom in Cwm.
Hello knowledgeable people!
I did a very stupid thing!... I took an official Samsung ROM package .tar.md5, remove the .md5 extension, extracted it, replaced boot.img with a custom kernel boot.img and re-compressed into a .tar package.
Then I took this .tar package and flashed it on the phone with Odin on my PC.
That didn't work, as expected.
The process blocked at one point.
I thought I will then just have to flash the Samsung official ROM to get everything back.
Well... not! I can flash the Samsung official ROM with Odin on my PC, but when the phone starts, it get stucked on bootloop on the glowing samsung logo.
I tried many things, including:
* wipe cache
* wipe data
but nothing worked...
At this point, I think I need to repartition/format everything and start from scratch but I don't know how to do this...
I tried to flash the Partition Identification Table kindly uploaded by @lyriquidperfection, but it didn't work (see here: http://forum.xda-developers.com/showthread.php?t=1950591) and it gets stuck in Odin as @narcarsiss mentions here: http://forum.xda-developers.com/showpost.php?p=33145970&postcount=2
Anyone has an idea?
> How to re-partition/re-format properly?
> Any other method to solve the bootloop?
Thanks for your help!
Why not to flash stock Sammy rom through Odin? This time - not modified?
Flash stock Sammy latest ROM .
Wipe everything in recovery and it should work.
I always have to wipe **** when installing official Sammy ROM.
Else it will stay at Samsung screen with flashing letters
Sent from my GT-I9305 using xda app-developers app
Hbohd said:
Why not to flash stock Sammy rom through Odin? This time - not modified?
Click to expand...
Click to collapse
This is what I tried... but it still get stuck at glowing samsung logo...
toeterbaas said:
Flash stock Sammy latest ROM .
Wipe everything in recovery and it should work.
I always have to wipe **** when installing official Sammy ROM.
Else it will stay at Samsung screen with flashing letters
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the answer.
What do you mean "wipe ****"?
Could you detail the steps?
1. Flash official sammy ROM through odin
2... enter recovery? (please confirm)
3... wipe what?
Thanks!
Have you tried flashing another kernel?Boeffla Etc then use KIES or Odin to flash back to stock
Sent from my GT-I9305 using xda app-developers app
Yes enter recovery after flashing with Odin.
When u power on hold volume up home key and power all at the same time release them when u see Samsung gt i9305 then wipe cach and wipe the other one. There are 2 wipe options.
Your phone should boot now it takes some time the first time around a minute.
Let me know if it worked
- flash stock Samsung ROM for your country with Odin
- go to recovery wipe the 2 options When u power on hold volume up home key and power all at the same time release them when u see Samsung gt i9305
-phone should boot takes a minute before he goes trough the flashing Samsung screen.
Sent from my GT-I9305 using xda app-developers app
---------- Post added at 09:51 AM ---------- Previous post was at 09:47 AM ----------
All you have to do is follow my steps.
It should work now
Sent from my GT-I9305 using xda app-developers app
Looki75 said:
Hello knowledgeable people!
I did a very stupid thing!... I took an official Samsung ROM package .tar.md5, remove the .md5 extension, extracted it, replaced boot.img with a custom kernel boot.img and re-compressed into a .tar package.
Then I took this .tar package and flashed it on the phone with Odin on my PC.
That didn't work, as expected.
The process blocked at one point.
I thought I will then just have to flash the Samsung official ROM to get everything back.
Well... not! I can flash the Samsung official ROM with Odin on my PC, but when the phone starts, it get stucked on bootloop on the glowing samsung logo.
I tried many things, including:
* wipe cache
* wipe data
but nothing worked...
At this point, I think I need to repartition/format everything and start from scratch but I don't know how to do this...
I tried to flash the Partition Identification Table kindly uploaded by @lyriquidperfection, but it didn't work (see here: http://forum.xda-developers.com/showthread.php?t=1950591) and it gets stuck in Odin as @narcarsiss mentions here: http://forum.xda-developers.com/showpost.php?p=33145970&postcount=2
Anyone has an idea?
> How to re-partition/re-format properly?
> Any other method to solve the bootloop?
Thanks for your help!
Click to expand...
Click to collapse
Tnx for the mention, but i heade bad news. I had to send my phone away to fix the issue.
This was a long time ago that this happened and better methods may of been discovered. Good luck:good:
narcarsiss said:
Tnx for the mention, but i heade bad news. I had to send my phone away to fix the issue.
This was a long time ago that this happened and better methods may of been discovered. Good luck:good:
Click to expand...
Click to collapse
Thanks for your answer!
I fear sending S3 to Samsung for repair is the only way, unfortunately... This is what I will do tomorrow (in 10hrs from now) unless a white knight arrives on this thread and gives me the golden solution!
You havent mentioned what rom version you tried.
I guess you used 4.3 official?
I could only guess but ther is probably more then just boot.img containing Knox code.
Knox is hindering users from downgrading bootloader and that maight be your problem now.
You did not mention wich version you try to recover to either.
So if you try with the old 4.1.2 it may be impossible.
Perhaps you need the newest official rom to get it working.
Sent from my GT-I9305 using XDA Premium 4 mobile app
tissot said:
You havent mentioned what rom version you tried.
I guess you used 4.3 official?
I could only guess but ther is probably more then just boot.img containing Knox code.
Knox is hindering users from downgrading bootloader and that maight be your problem now.
You did not mention wich version you try to recover to either.
So if you try with the old 4.1.2 it may be impossible.
Perhaps you need the newest official rom to get it working.
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your answer.
The home made package was on 4.3 base.
Then I tried to reflash official 4.3.
I will give a try with 4.1.2...
Well... didn't work either... since I already had knox bootloader...
It shows "unsupported version".
Oh well...
tissot said:
You havent mentioned what rom version you tried.
I guess you used 4.3 official?
I could only guess but ther is probably more then just boot.img containing Knox code.
Knox is hindering users from downgrading bootloader and that maight be your problem now.
You did not mention wich version you try to recover to either.
So if you try with the old 4.1.2 it may be impossible.
Perhaps you need the newest official rom to get it working.
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can't flash the old version. Odin will revert it back while installing.
Sent from my GT-I9305 using xda app-developers app
Looki75 said:
Thanks for your answer.
The home made package was on 4.3 base.
Then I tried to reflash official 4.3.
I will give a try with 4.1.2...
Click to expand...
Click to collapse
Okey
A bit far feched but is it possible your download is broken? Try DL again.
And either it is or not you could try installing 4.3 from different region as yours. Just to try every possability.
It shouldnt be impossible to fix this stupid phone
You dont have any nandroid backup some where.
Last option. Throw it on a brick wall to release som aggrevation and then you buy a Nexus 5. Problem solved.
Sent from my GT-I9305 using XDA Premium 4 mobile app
tissot said:
Okey
A bit far feched but is it possible your download is broken? Try DL again.
And either it is or not you could try installing 4.3 from different region as yours. Just to try every possability.
It shouldnt be impossible to fix this stupid phone
You dont have any nandroid backup some where.
Last option. Throw it on a brick wall to release som aggrevation and then you buy a Nexus 5. Problem solved.
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You made me laugh!
Seriously: DL is OK (I flashed this very official ROM many times in the past) and I do have a nandroid, but result is the same (stuck at glowing samsung logo).
The issue is way deeper.
Thanks for your help! Before trying the brick wall, I will try to make it repaired by Samsung!
Looki75 said:
You made me laugh!
Seriously: DL is OK (I flashed this very official ROM many times in the past) and I do have a nandroid, but result is the same (stuck at glowing samsung logo).
The issue is way deeper.
Thanks for your help! Before trying the brick wall, I will try to make it repaired by Samsung!
Click to expand...
Click to collapse
I had a brick once, butthe situation was a bit different. I have knox bootloader and tried to downgrade to a 4.1.2 rom without the bootloader package. The flash went ok, but my phone was stucked on Samsung Galaxy S3 GT-I9305 screen. After that, i was quite desperate and tried to reflash stock 4.3 via odin, but it failed :S
Then i tried to flash official Germany's 4.3 again, this time with the ODIN version inside CF-Root package (http://download.chainfire.eu/232/CF-Root1/CF-Auto-Root-m3-m3zh-gti9305.zip?retrieve_file=1), put the cable in another USB port, killed every kies proccess and rebooted phone in dowwnload mode. This time the flash went ok, i rebooted the phone into recovery (got bootloop) and wipe cache and factory reset. After this the phone booted up normally. Hope you can fix your phone
shucrut said:
I had a brick once, butthe situation was a bit different. I have knox bootloader and tried to downgrade to a 4.1.2 rom without the bootloader package. The flash went ok, but my phone was stucked on Samsung Galaxy S3 GT-I9305 screen. After that, i was quite desperate and tried to reflash stock 4.3 via odin, but it failed :S
Then i tried to flash official Germany's 4.3 again, this time with the ODIN version inside CF-Root package (http://download.chainfire.eu/232/CF-Root1/CF-Auto-Root-m3-m3zh-gti9305.zip?retrieve_file=1), put the cable in another USB port, killed every kies proccess and rebooted phone in dowwnload mode. This time the flash went ok, i rebooted the phone into recovery (got bootloop) and wipe cache and factory reset. After this the phone booted up normally. Hope you can fix your phone
Click to expand...
Click to collapse
Thanks! Any idea is valuable!
How did you create the ball pack of "4.1.2 rom without the bootloader" - in other words: how did you remove the bootloader from there?
Looki75 said:
Thanks! Any idea is valuable!
How did you create the ball pack of "4.1.2 rom without the bootloader" - in other words: how did you remove the bootloader from there?
Click to expand...
Click to collapse
I'd used this tutotial (just the part of commands, added everything that the original ".md5" has, removing just the "sboot.img", i'm not 100% sure if this is the only file to be off the new package, as i said, didnt work for me ), the only difference is that i'm using cygwin instead of linux itself, it worked like a charm
Basically all u need to do is unpack a original .md5 firmware (use winrar or so) and move the files (except sboot.img) to your home directory of linux or, in my case, cygwin (originally C:\cygwin\home\user-name), start the console and type the command bellow, switching the ".imgs" to match yours, of course:
Code:
cd $HOME
tar -H ustar -c image_1 image_2 > your_odin_package.tar
After this you must have a 1Gb+ .tar file (considering you will make a stock samsung flashable), now you will add md5 checksum to that, just to avoid troubles:
Code:
md5sum -t your_odin_package.tar >> your_odin_package.tar
mv your_odin_package.tar your_odin_package.tar.md5
and voilà, you have your flashable odin package. Of course you can try making one with just the system.img, boot.img and modem.img. If the phone boots up, do a factory reset. I have no idea if this will work in any occasion having knox bootloader trying to flash official 4.1.x, but you can also try with a samsung 4.3 rom.
In the last scenario, try to CF auto-root your phone, then flash an official CWM recovery via odin using this method i told u, boot into recovery and flash a custom rom, do a factory reset and wiping cache and dalvik cache. I hope one of the options work for you.
I'd recommend trying to flash a custom recovery and then a custom rom. If phone boots up and is functional, try to flash samsung official 4.3 again (if your desire is having the stock of course), not forgeting to factory reset via cwm first to avoid troubles.
Been in maybe like pratically the same situation
1st flash philz touch recovery ( install latest version)
2nd backup ur efs in external sd and copy it to a pc just in case (important if u mess up imei )
3rd Copy and rom in the external sd
4th Wipe data,cache,dilvik
5th In mount and storage Format everything except external sd ( u can backup ur internal sd card with 3rd step)
6th Flash Rom and reboot
7th If no imei then try a newer modem
http://forum.xda-developers.com/showthread.php?t=2572432
http://forum.xda-developers.com/showthread.php?t=2607279
Notice I only could get to run 4.3 to run after formating everything through philz touch recovery
Hi,
i am stuck in a bootloop.
i have an unlocked bootloader and had CM10.1 previously.
i then went back to an old 20a backup i made some month ago.
that worked fine.
my phone downloaded an update to 20b then, and i installed it.
after that i am stuck in a bootloop now. normal booting gives me cwm.
i am not able to turn the phone off and charge it, as mentioned somewhere else, to clear the "boot to recovery" flag.
someone knows a way to clear this flag?
Its not important for me if i run stock or CM, but even when i install my CM backup now it still boots into recovery.
holding <down> while rebooting gives me "S/W Upgrade - Please wait while upgrading".
it seems the 20b update is still present and trying to boot into stock recovery, resulting in cwm getting loaded everytime.
(cwm works fine, i can upload a zip and execute it)
greetings
LamerDuck said:
Hi,
i am stuck in a bootloop.
i have an unlocked bootloader and had CM10.1 previously.
i then went back to an old 20a backup i made some month ago.
that worked fine.
my phone downloaded an update to 20b then, and i installed it.
after that i am stuck in a bootloop now. normal booting gives me cwm.
i am not able to turn the phone off and charge it, as mentioned somewhere else, to clear the "boot to recovery" flag.
someone knows a way to clear this flag?
(cwm works fine, i can upload a zip and execute it)
greetings
Click to expand...
Click to collapse
i had the same, if you want to install ota updates you should have the "original" recovery.
i flashed it back to stock with LG .kdz flasher. if i remember correct flashing a backup from sd card won't slove this problem.
Greetings
moneyvirus
moneyvirus said:
i had the same, if you want to install ota updates you should have the "original" recovery.
i flashed it back to stock with LG .kdz flasher. if i remember correct flashing a backup from sd card won't slove this problem.
Greetings
moneyvirus
Click to expand...
Click to collapse
hm, i remember having the same problem while installing CM. there was something i did to interrupt the loop, and yes, i think the original LG suite or kdz was involved. but i should not need to reflash the original rom.. its just a flag, i should be able to clear it with sideload/zip/button combination.
[edit] maybe i wasnt clear about that: i dont need the 20b upgrade, i would love to cancel the update process, if that makes my phone boot again.
LamerDuck said:
hm, i remember having the same problem while installing CM. there was something i did to interrupt the loop, and yes, i think the original LG suite or kdz was involved. but i should not need to reflash the original rom.. its just a flag, i should be able to clear it with sideload/zip/button combination.
[edit] maybe i wasnt clear about that: i dont need the 20b upgrade, i would love to cancel the update process, if that makes my phone boot again.
Click to expand...
Click to collapse
sorry but i can't help you with the flag... i solved it by reflashing but i have to admit it's quite drastic.
well..
i will reflash stock i guess.
do you remember which thread/tool/drivers you used to reflash?
i am on win7 and my PC isnt able to load fastboot nor LG mobile usb drivers.
i have them installed but get the yellow warning on both in windows hardware administration page
LamerDuck said:
well..
i will reflash stock i guess.
do you remember which thread/tool/drivers you used to reflash?
i am on win7 and my PC isnt able to load fastboot nor LG mobile usb drivers.
i have them installed but get the yellow warning on both in windows hardware administration page
Click to expand...
Click to collapse
it's allready a lot of months a go but i think i used this thread.
http://forum.xda-developers.com/showthread.php?t=2179126
Goodluck m8
LamerDuck said:
well.. i will reflash stock i guess.(
Click to expand...
Click to collapse
Easiest way to reflash stock is to force an update using the LGMobile Support Tool. Once your phone is connected (I suggest the S/W Update mode) look for the option somewhere in the upper right menu.
Edit: This will also revert to the stock recovery.
balloon27 said:
Easiest way to reflash stock is to force an update using the LGMobile Support Tool. Once your phone is connected (I suggest the S/W Update mode) look for the option somewhere in the upper right menu.
Edit: This will also revert to the stock recovery.
Click to expand...
Click to collapse
if i recall correctly, the LGMobile Support Tool tool wont recognize my phone, since i have a custom kernel, unlocked bootloader and a custom ROM.
i am trying to flash stock ROM now with kdz updater ( http://forum.xda-developers.com/showthread.php?t=2069723 ), and if this does not work i am going through every method thats there..
total overkill for a working phone thats just too stupid to boot the right option..
@moneyvirus: thx
LamerDuck said:
if i recall correctly, the LGMobile Support Tool tool wont recognize my phone, since i have a custom kernel, unlocked bootloader and a custom ROM.
Click to expand...
Click to collapse
Not sure about this, but the S/W mode might make a difference here. No harm in trying, right?
well. i was able to install stock 20a with kdz updater and link above.
cwm is gone now ofc, but everything at least works.
in some hours i will be rooted and cwm'ed again, but well... its always the same lesson: never touch a running system.
but maybe here's the wrong place to insist on this wisdom
I followed the steps in Neo's thread about repartitioning and ended up in sh** where I can not see sdcard0 (internal memory) and phone says there is no micro sd card inserted even though it is.
I tried with terminal commands to fix storage permissions, but it doesn't allow me anything as it says files are read only.
I flashed the uninstaller as well which says it should help and did not help.
Any other ideas? :/
_ronin_ said:
I followed the steps in Neo's thread about repartitioning and ended up in sh** where I can not see sdcard0 (internal memory) and phone says there is no micro sd card inserted even though it is.
I tried with terminal commands to fix storage permissions, but it doesn't allow me anything as it says files are read only.
I flashed the uninstaller as well which says it should help and did not help.
Any other ideas? :/
Click to expand...
Click to collapse
Which recovery is installed? Try AdrianDC's latest TWRP. Also CM13 might help as it will repartion the storage.
St.Jimmy90 said:
Which recovery is installed? Try AdrianDC's latest TWRP. Also CM13 might help as it will repartion the storage.
Click to expand...
Click to collapse
Thank you very much for answer, almost gave up on the phone pretty much.
Twrp is 2.8.xxx something (one supplied with Neo's rom), I tried with 3.0 did not help. Tried with Clockworkmod didnt help either.
I will search for AdrianDC TWRP and give it a go.
Cm13 I tried but did not want to apply the storage change because it could not find "system" partition, (almost bricked it I guess) but I managed to fix that with stock rom, and could later reflash cm 12.1
But I will try flashing CM13 again, and come back with info in case you will be able to give some input again!
Thanks for now!
_ronin_ said:
Thank you very much for answer, almost gave up on the phone pretty much.
Twrp is 2.8.xxx something (one supplied with Neo's rom), I tried with 3.0 did not help. Tried with Clockworkmod didnt help either.
I will search for AdrianDC TWRP and give it a go.
Cm13 I tried but did not want to apply the storage change because it could not find "system" partition, (almost bricked it I guess) but I managed to fix that with stock rom, and could later reflash cm 12.1
But I will try flashing CM13 again, and come back with info in case you will be able to give some input again!
Thanks for now!
Click to expand...
Click to collapse
No worries.
For the recovery, go here:
http://forum.xda-developers.com/xpe...t/recovery-twrp-3-0-0-touch-recovery-t3319588
And CM13 here:
http://forum.xda-developers.com/xperia-t-v/orig-development/rom-cyanogenmod-13-0-xperia-t-t3415827
I'm using it on my T and it's pretty awesome
St.Jimmy90 said:
No worries.
For the recovery, go here:
http://forum.xda-developers.com/xpe...t/recovery-twrp-3-0-0-touch-recovery-t3319588
And CM13 here:
http://forum.xda-developers.com/xperia-t-v/orig-development/rom-cyanogenmod-13-0-xperia-t-t3415827
I'm using it on my T and it's pretty awesome
Click to expand...
Click to collapse
Cheers for links, Tried with CM13, no success like before getting error when flashing the zip:
"sdcard could not be mounted (ext4/exfat ?) please verify your partition file system
You are agreeing to format your SDCard
UserData partition still contains files"
so doesnt let me flash 13.
And to repair the partitions I guess I just try the TWRP and under advance the repair option right?
Terribly sorry to bother so much, but I like the phone, and would love to fix it again!
_ronin_ said:
Cheers for links, Tried with CM13, no success like before getting error when flashing the zip:
"sdcard could not be mounted (ext4/exfat ?) please verify your partition file system
You are agreeing to format your SDCard
UserData partition still contains files"
so doesnt let me flash 13.
And to repair the partitions I guess I just try the TWRP and under advance the repair option right?
Terribly sorry to bother so much, but I like the phone, and would love to fix it again!
Click to expand...
Click to collapse
Try to flash twrp first. Then do a reboot and try again to flash cm13.
Please report back how it goes
Good luck
St.Jimmy90 said:
Try to flash twrp first. Then do a reboot and try again to flash cm13.
Please report back how it goes
Good luck
Click to expand...
Click to collapse
Done and done, but I basically ended up on the same spot where it said unable to mount /system + previous error about sdcard
and now can not flash anything anymore (so have to flash official rom again to start up my phone)
Maybe im doing something wrong with flashing, but i doubt it. (flashtool64 is which im using) fastboot, and under the option of select kernel to flash.
then rest is done in recovery anyway with installing, right?
At the moment I am installing official rom, so I can start over with flashing twrp, rebooting, then flashing cm13
One thing I learned to always backup working system before doing anything!
_ronin_ said:
Done and done, but I basically ended up on the same spot where it said unable to mount /system + previous error about sdcard
and now can not flash anything anymore (so have to flash official rom again to start up my phone)
Maybe im doing something wrong with flashing, but i doubt it. (flashtool64 is which im using) fastboot, and under the option of select kernel to flash.
then rest is done in recovery anyway with installing, right?
At the moment I am installing official rom, so I can start over with flashing twrp, rebooting, then flashing cm13
One thing I learned to always backup working system before doing anything!
Click to expand...
Click to collapse
I'm sorry to hear that.
Once stock rom is on it, try to flash neos kernel and then boot into recovery. In there flash Adriandc's twrp (the zip file).
After that reboot and try to flash cm13. If this still doesn't work you could try Adriandc's files for repartitioning. He did some awesome work.
I'm on my phone right now so I'll keep it short, if you need further assistance I'll try to help you as soon as i get to my PC
St.Jimmy90 said:
I'm sorry to hear that.
Once stock rom is on it, try to flash neos kernel and then boot into recovery. In there flash Adriandc's twrp (the zip file).
After that reboot and try to flash cm13. If this still doesn't work you could try Adriandc's files for repartitioning. He did some awesome work.
I'm on my phone right now so I'll keep it short, if you need further assistance I'll try to help you as soon as i get to my PC
Click to expand...
Click to collapse
Thanks!
Tried exactly like that, same error when trying to flash cm13 :"Updater process ended with ERROR:7
Error installing zip file ".zip"
I guess I ruined something really bad when trying to repartion following neo's guide, (twrp says about partitions this:
- Internal storage: (1812mb)
- Legacy SDCard (0mb)
- Micro SDCard (7488mb)
-USB OTG (0mb)
If you have any more suggestions I can try, otherwise we can give up! feels like nothing would work, though much love for taking your time trying to help me! <3
_ronin_ said:
Thanks!
Tried exactly like that, same error when trying to flash cm13 :"Updater process ended with ERROR:7
Error installing zip file ".zip"
I guess I ruined something really bad when trying to repartion following neo's guide, (twrp says about partitions this:
- Internal storage: (1812mb)
- Legacy SDCard (0mb)
- Micro SDCard (7488mb)
-USB OTG (0mb)
If you have any more suggestions I can try, otherwise we can give up! feels like nothing would work, though much love for taking your time trying to help me! <3
Click to expand...
Click to collapse
It doesn't look that bad at all. Which version of TWRP is currently on your phone? (also the build date)
It looks like basketbuild is down right now, but once it's back up again you could try this zip:
https://basketbuild.com/devs/AdrianDC/CyanogenMod/XperiaBlue
it will repartition your phone to it's original partition table
St.Jimmy90 said:
It doesn't look that bad at all. Which version of TWRP is currently on your phone? (also the build date)
It looks like basketbuild is down right now, but once it's back up again you could try this zip:
https://basketbuild.com/devs/AdrianDC/CyanogenMod/XperiaBlue
it will repartition your phone to it's original partition table
Click to expand...
Click to collapse
Oh that sounds exactly what I would need yea!
At the moment I reflashed cm12.1 (neo's) which installs 2.8.6.x twrp. Build date was january i think. (phone is booting up still)
I will try this zip as soon as basketbuild is up and will let you know what happens. (I guess i just reboot into twrp and flash the zip)?
_ronin_ said:
Oh that sounds exactly what I would need yea!
At the moment I reflashed cm12.1 (neo's) which installs 2.8.6.x twrp. Build date was january i think. (phone is booting up still)
I will try this zip as soon as basketbuild is up and will let you know what happens. (I guess i just reboot into twrp and flash the zip)?
Click to expand...
Click to collapse
Yeah, boot into TWRP, flash a new TWRP (I think it was 20th july or newer), then reboot straight into recovery again and flash the restore_sd zip
My phone booted up now with the 12.1, and there is internal memory back, 11gb out of 11gb free, accessable, and everything.. No idea what caused it to appear again but something what you said basically helped me and restored it back to original.
So thank you a lot! I kinda want to try and repartition it again to have more space for apps, but im afraid ill just blow it again.
You think I should try installing cm13 now as storage looks normal again?
_ronin_ said:
My phone booted up now with the 12.1, and there is internal memory back, 11gb out of 11gb free, accessable, and everything.. No idea what caused it to appear again but something what you said basically helped me and restored it back to original.
So thank you a lot! I kinda want to try and repartition it again to have more space for apps, but im afraid ill just blow it again.
You think I should try installing cm13 now as storage looks normal again?
Click to expand...
Click to collapse
I'm really glad you managed to restore it! Mint is still a great device.
Yeah, but CM13 will repartition your phone again (automatically). It will warn you once that all data will be lost, on second attempt it will flash just fine.
Good luck
St.Jimmy90 said:
I'm really glad you managed to restore it! Mint is still a great device.
Yeah, but CM13 will repartition your phone again (automatically). It will warn you once that all data will be lost, on second attempt it will flash just fine.
Good luck
Click to expand...
Click to collapse
Yep it did just that. Im very grateful for all help, running cm13 now as well, and storage wont be an issue anymore it seems!
_ronin_ said:
Yep it did just that. Im very grateful for all help, running cm13 now as well, and storage wont be an issue anymore it seems!
Click to expand...
Click to collapse
Awesome. Have fun with CM13, it's really a great rom.