Guest Mrtransformer124 Posted January 3, 2013 Report Posted January 3, 2013 i tried the ics mods now it wont boot
Guest BlueMoonRising Posted January 3, 2013 Report Posted January 3, 2013 i tried the ics mods now it wont boot Just had the same problem using flibblesans mods, says cannot find directory although it looks correct to me. Exit the tool and use task manager to kill any remaining adb.exe. Turn the phone off and then hold down the camera button while turning back on and you should get the androidboot animation. Start the tool and wait a moment until it finds the phone, use fixbrick and wait. When it's finished you'll need to root again.
Guest Mrtransformer124 Posted January 3, 2013 Report Posted January 3, 2013 what tool? because i did it the manual way
Guest Mrtransformer124 Posted January 3, 2013 Report Posted January 3, 2013 please please i dont understand any of this stuff i need to fix it quickly when i do the camera button it still boots into loop and it says device not found on AIO san diego tools
Guest BlueMoonRising Posted January 3, 2013 Report Posted January 3, 2013 what tool? because i did it the manual way The AIO san diego tool.
Guest Mrtransformer124 Posted January 3, 2013 Report Posted January 3, 2013 ah yes that how do u use it because when i tried power+camera it didnt come up with anything so i tried power+volume buttons and it bought me to a droidboot screen. what to do from there
Guest Mrtransformer124 Posted January 3, 2013 Report Posted January 3, 2013 says error device not found
Guest Mrtransformer124 Posted January 3, 2013 Report Posted January 3, 2013 so do i put update.zip in the sandiego tmp folder before try to fix brick?
Guest BlueMoonRising Posted January 3, 2013 Report Posted January 3, 2013 so do i put update.zip in the sandiego tmp folder before try to fix brick? The Xolo.zip (299MB in size) should already be in C:\SanDiego\tools\bricked
Guest Mrtransformer124 Posted January 3, 2013 Report Posted January 3, 2013 no it isnt but i have a copy shud i psate it there and try again?
Guest BlueMoonRising Posted January 3, 2013 Report Posted January 3, 2013 says error device not found You may need to unplug the phone, wait a few seconds and then plug it back in. Be patient each time and give it a minute to find the device.
Guest Mrtransformer124 Posted January 3, 2013 Report Posted January 3, 2013 thank u so much man, a big help to me, +1 to you :D
Guest bravo76pk Posted January 3, 2013 Report Posted January 3, 2013 having same problem... but when i try to fix it by unbricking it sends the update file and flashes it but when in recovery green bot shows it starts to write but all of a suddent turns into red exclaimation this is now happening in a loop cant get out of it any help ?? thanks
Guest Simon O Posted January 4, 2013 Report Posted January 4, 2013 There was a typo in my mod script which didn't set permissions on a few files but that still shouldn't had caused a boot loop. I do apologise if using the mod pack has caused a problem for you though.
Guest Ced_Gee Posted January 4, 2013 Report Posted January 4, 2013 It caused mine to bootloop too, the updated script has sorted it out now though. Thanks.
Guest Posted February 26, 2013 Report Posted February 26, 2013 mine is now on a bootloop any ideas how to fix it? its got xolo x900 rom on from the aio tool, but since applying the xolo900 stock pack and trying debranding its stuck on the intel screen looping scott ps i can get onto the droidboot screen but no further
Guest utternoob Posted February 26, 2013 Report Posted February 26, 2013 Run fix brick in tool (option 1)
Guest amirsamdani Posted June 23, 2013 Report Posted June 23, 2013 (edited) I am having same problem with my San Diego ina bootloop. I had an issue with adbd insecure app which was having superuser permission denied therefore used "AIO Auto For Xolo" but after using it I could not get the phone to pass bootloop! I tried to run fix brick in tool (option 1) but that does not help me as well Something weird I hav noticed, in this bootloop When I pressed power button screen went purple ( it happened in first two press then screen was showing dim light) Any help is appreciated Edited June 23, 2013 by amirsamdani
Guest BlueMoonRising Posted June 24, 2013 Report Posted June 24, 2013 I am having same problem with my San Diego ina bootloop. I had an issue with adbd insecure app which was having superuser permission denied therefore used "AIO Auto For Xolo" but after using it I could not get the phone to pass bootloop! I tried to run fix brick in tool (option 1) but that does not help me as well Something weird I hav noticed, in this bootloop When I pressed power button screen went purple ( it happened in first two press then screen was showing dim light) Any help is appreciated Presuming you've not installed any of the updates then try http://www.modaco.com/topic/362692-another-osd-bricked/#entry2126154
Guest amirsamdani Posted June 24, 2013 Report Posted June 24, 2013 Presuming you've not installed any of the updates then try http://www.modaco.co...d/#entry2126154 Thanks for coming back to me. I have the step you mentioned to use fixbrick, here where I am stuck The phone should be unplugged, hold power button until you feel it vibrate(this should shut it down). OK Hold power button and vol- until it vibrates, this should put it into droidboot screen. OK Start task manager in windows and kill any adb.exe running. OK Start the AIO tool and plug in the phone(make sure it's awake, it's a very short screen off time). This is where i got problem As soon as a conenct phone with USB it seems to be showing different colors on screen - which I think phone is trying to boot as normal. AIO tool is not able to detect the phone.
Guest BlueMoonRising Posted June 24, 2013 Report Posted June 24, 2013 Thanks for coming back to me. I have the step you mentioned to use fixbrick, here where I am stuck The phone should be unplugged, hold power button until you feel it vibrate(this should shut it down). OK Hold power button and vol- until it vibrates, this should put it into droidboot screen. OK Start task manager in windows and kill any adb.exe running. OK Start the AIO tool and plug in the phone(make sure it's awake, it's a very short screen off time). This is where i got problem As soon as a conenct phone with USB it seems to be showing different colors on screen - which I think phone is trying to boot as normal. AIO tool is not able to detect the phone. Have a look at http://www.modaco.com/topic/362574-solved-problem-of-screen-flashing-different-colors-after-flashing-updatezip-after-installing-37mb-or-12mb-update-on-xolo-ics-rom/#entry2124098 then.
Guest amirsamdani Posted June 24, 2013 Report Posted June 24, 2013 Have a look at http://www.modaco.co...m/#entry2124098 then. This is what my next move is, already orders HDMI cable for san diego, will see if this can help ( hopefully) :(
Guest amirsamdani Posted June 25, 2013 Report Posted June 25, 2013 (edited) This is what my next move is, already orders HDMI cable for san diego, will see if this can help ( hopefully) :( Bad news :(...I connected phoned with TV using HDMI but after Xolo logo appearing on the phone nothing appear on TV. Little good news is that when I whitched the phone by holding power button and volume(-) button I can see droidboot screen, then if I try to move to stock recovery by holding power and volume(+) nothing come up :( Eventually I managed to get phone connected with TV and got update installed - all sorted. thx for your support Edited June 26, 2013 by amirsamdani
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now