Related
Ok, I tried to search and cannot find a fix for this. I managed to load an expired Beta ROM on my phone. Now I cannot connect via activesync to load another one that functions. I just get a screen that says
" This concludes the BETA testing of this software release........"
Some one please help, I tried searching, but could not find anything.
Thanks everyone. I guess this is what I get for playing with different ROMs.
Flash a new one by SD Card then
Thanks, I will search on how to do that.
Thanks
Downloaded Factory ROM and loaded from Bootloader.
THanks
Yep, you still can enter bootloader and load another rom.
dmoney69 said:
Ok, I tried to search and cannot find a fix for this. I managed to load an expired Beta ROM on my phone. Now I cannot connect via activesync to load another one that functions. I just get a screen that says
" This concludes the BETA testing of this software release........"
Some one please help, I tried searching, but could not find anything.
Thanks everyone. I guess this is what I get for playing with different ROMs.
Click to expand...
Click to collapse
I’ve faced the same problem try below link :
http://wiki.xda-developers.com/index.php?pagename=Hermes_Resets
It worked…
Cheers
VIB>>>
This concludes the BETA testing of this software release........"
I had same problem and try to reset but it did not work. Please Help!
Thank you.
pakinfv said:
I had same problem and try to reset but it did not work. Please Help!
Thank you.
Click to expand...
Click to collapse
Did you try the options already stated in this thread?
You can put the phone in bootloader and flash the stock (or shipped rom) or flash another rom using the sd method (like the at&t stripped). Then you might want to also do some reading before you flash again, just to make sure you know how to unbrick.
This has been stated many times around the forums, and on the wiki.
To put your phone into boot loader hold the left ok key and the power button at the same time and hit the reset key with the stylus.
The info for flashing via the sd method is in the wiki, and I believe flashing from bootloader is there too.
The search button up there between "New Posts" and "Quick Links" is a good friend for the information hungry. This phone is old enough that I would guess any problem you have, has been experienced and solved by someone else already.
pakinfv said:
try to reset but it did not work.
Click to expand...
Click to collapse
and it WON'T work. You cannot fight with this for yourself, it requires fixing a ROM itself. Just do what others said earlier, what they were writing for?....
Go to the bootloader and flash another ROM.
Please close thread. Asked / Answered...Resolved.
hey,
my girlfriend has a moto defy and im quite in to getting it going to display its full potential as i am sure the this device is not great in its stock state and it seems to have some dugs e.g. freezing a lot etc... you all know what i mean haha. she has not quite grasped the fact that the device will be 1000 times better with a nice build of cm7 but i am having issues with the bootloader and installing cwm based recovery so can you guys give me a step by step guide on how to get this going i would like to see how it takes ics and if they have fixed the issue with the hardware accelerator
thanks a lot if you can help p.s. can you send me the message on the private message option as i will be over at the p6200 tab plus section and not on er haha
Okay.
EDIT2: ***Im tired** sorry. We need root too!
Use superoneclick to root.
Because i've had to edit twice, it's better you read this LOL
http://www.freeyourandroid.com/guide/root-motorola-defy
So, first you need to get ADB. EDIT: This is unecessary! But useful anyway!
This is quite a long process, so follow this guide
Next, you need to get 2nd init, this installs a custom recovery app, which you use to get CM7. Just install the app on the phone, and press install 2nd init.
When it reboots, press the volume key when the LED flashes blue for a couple of seconds.
It is attached.
Okay, now find your chosen rom (plenty on here)
Download it, and put it on your sd card, then install using 2nd init.
Don't forget to follow all instructions!
MainCourse said:
Okay.
EDIT2: ***Im tired** sorry. We need root too!
Use superoneclick to root.
Because i've had to edit twice, it's better you read this LOL
http://www.freeyourandroid.com/guide/root-motorola-defy
So, first you need to get ADB. EDIT: This is unecessary! But useful anyway!
This is quite a long process, so follow this guide
Next, you need to get 2nd init, this installs a custom recovery app, which you use to get CM7. Just install the app on the phone, and press install 2nd init.
When it reboots, press the volume key when the LED flashes blue for a couple of seconds.
It is attached.
Okay, now find your chosen rom (plenty on here)
Download it, and put it on your sd card, then install using 2nd init.
Don't forget to follow all instructions!
Click to expand...
Click to collapse
i have thanked u bro haha great help thanks very much
i really could kiss u haha but i choose not to lol
Hello All,
First time post and as an offering, I will say 'thanks' to anyone that responds in a positive manner to my post (trying to win some friends) :laugh:
Here's my issue, I have an Arc S LT18i.
Unlocked bootloader and rooted.
Whenever I flash anything custom the touch screen fails to respond, i've flashed LupusV7, slim bean 3.1 and 3.2 (with arc fusion 3.6 and 4.5) and Super Jelly Bean. All seemingly start without any issues and the physical buttons work no problem. BUT the screen refuses to work in anyway at all!!
I have made sure I wiped the system, cache and delvak (sp?)
Any help greatly appreciated, I am a NOOB but underneath it all I'm just trying to make the most of this wonderful Arc S...
Anything you want to know, please ask away...
Please help.
Namaste
Ricky:fingers-crossed:
Try doing a clean install
- Flash stock ICS .587 ftf
- Flash Kernel
- Wipe data,cache & dalvik
- Install ROM
sent via XPERIA™
Same thing!!
msc3169 said:
Try doing a clean install
- Flash stock ICS .587 ftf
- Flash Kernel
- Wipe data,cache & dalvik
- Install ROM
sent via XPERIA™
Click to expand...
Click to collapse
Hello and thank you for the reply...
I flashed stock ICS .587 (world india) from this site talk.sonymobile.com/thread/35239
Does that count as stock ICS .587?
And then followed the rest of the instructions, the exact same thing happens... buttons work but the touch screen does not!?
Any other ideas please? Or does anyone else have a suggestion?
Thank you very much for taking the time to reply to me.
Ricky
ricky7D said:
Hello and thank you for the reply...
I flashed stock ICS .587 (world india) from this site talk.sonymobile.com/thread/35239
Does that count as stock ICS .587?
And then followed the rest of the instructions, the exact same thing happens... buttons work but the touch screen does not!?
Any other ideas please? Or does anyone else have a suggestion?
Thank you very much for taking the time to reply to me.
Ricky
Click to expand...
Click to collapse
Are you using compatible ROM and Kernel?
僕のLT18iから送られてきた
compatible ROM and Kernel
popthosegaskets said:
Are you using compatible ROM and Kernel?
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Hello, thanks for the reply...
According to the Slim Bean page, I can use ANY kernel with that rom. But also, if I just have the Lupusv7 Kernel on there, the touch screen doesn't work within that, so not a ROM/Kernel conflict I belive.
I've also tried other Kernel/ROM combinations, same thing keeps on happening. Touchscreen works 100% with a SE restore, stock ROM.
Any other ideas please??
ricky7D said:
Hello, thanks for the reply...
According to the Slim Bean page, I can use ANY kernel with that rom. But also, if I just have the Lupusv7 Kernel on there, the touch screen doesn't work within that, so not a ROM/Kernel conflict I belive.
I've also tried other Kernel/ROM combinations, same thing keeps on happening. Touchscreen works 100% with a SE restore, stock ROM.
Any other ideas please??
Click to expand...
Click to collapse
It's best to use the recommended kernel as stated on the ROM thread. Try another kernel and see how things go.
僕のLT18iから送られてきた
You sure you installed device-specific patch / chose correct phone in AROMA?
Kernel or ROM issue?
popthosegaskets said:
It's best to use the recommended kernel as stated on the ROM thread. Try another kernel and see how things go.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Hello,
As previously mentioned, the reccomended kernel is Lupusv7, When i flash this Kernel into recovery mode, all looks well but as it has a touch screen interface this still doesn't work!
I'm presuming that it cannot be a conflict as it's happen before I instll the new ROM etc... the touch screen doesn't even work within the GUI of the Lupusv7 kernel.
I can get multiple ROMS to load with different kernels but so far, none have booted with the touch screen working!!
I am very much a noob but have read loads of articles on how this should be done, unless i'm missing something very obvious which isn't stated then I dont see anyone else having this issue.
Any clues people? :good:
Thanks, Ricky
AROMA?
Someguyfromhell said:
You sure you installed device-specific patch / chose correct phone in AROMA?
Click to expand...
Click to collapse
Hello Someguyfromhell,
I haven't used AROMA, the guides i've been reading haven't mentioned this!?
This is the process I went through:
flashed stock ICS ROM
flashed kernel
wipe data/cache/davlik
flashed rom
rebooted, ROM loads up and the touch screen doesn't work.
Any help you can give me on AROMA, links etc?
I'm looking right now, but a 'leg up' would be great.
Thanks for the reply.
Ricky
here what to do
- Make sure you had installed Official 4.0.4 ftf pack
- When flashing official ftf pack remember to exclude / tick these things:
1. simlock.ta (Exclude TA)
2. Kernel.sin (Exclude kernel)
3. FOTA (Exclude FOTA)
After flash successful, power on your phone and let it start completely
- Now you can start to install any ROM
1.Flash the Recommended Kernel: Vengeance , KTG Anzu , RUSH
2. Place ROM on SD card
3. Power off the phone and boot into CWM
3. Backup and restore > choose Backup
4. Wipe Data/Factory Reset
5. Mounts and storage > Format /system
6. Advanced > Wipe battery stats
7. Install zip from SD card > Choose the rom
8. if rom uses aroma Follow on screen instructions on AROMA, remember to choose "Unlocked bootloader" and also the correct kernel modules and of course the correct phone model
9. After complete installation tick "Reboot" and let the phone restart
10. Give the phone a good full charge, and enjoy ur phone !
11.THE MOST IMPORTANT THING PRESS THANKS if I helped
ricky7D said:
Hello Someguyfromhell,
I haven't used AROMA, the guides i've been reading haven't mentioned this!?
This is the process I went through:
flashed stock ICS ROM
flashed kernel
wipe data/cache/davlik
flashed rom
rebooted, ROM loads up and the touch screen doesn't work.
Any help you can give me on AROMA, links etc?
I'm looking right now, but a 'leg up' would be great.
Thanks for the reply.
Ricky
Click to expand...
Click to collapse
Then did you install the device-specific patch?
ok man, you've got the same problem like me
First thing, all roms that make your touch screen doesn't work will based on cm (e.g. cm10, slim, any jb).
and ALL STOCK roms will get no problem.
There's lot of people here got this problem and still has no clue why this problem occure to ours, so sad story.
Someone says that the touch screen firmware sould be updated to the lastest version, but i don't know how.
One solution that i found is, remove the battery to turn off then turn it on to reboot again and again. If you lucky enough, the touch screen will work like a miracle!
and the success rate is also <50% ( based on my experience only)
AROMOA guide?
Someguyfromhell said:
Then did you install the device-specific patch?
Click to expand...
Click to collapse
on all the ROM guides, I have never seen a part where it says i should install a device specific patch, do you have a link to where these may be?
Or even a ROM with guide where it says this? I'm very happy to follow that to get this working. I have no preference to CM10, Slim Bean, Racing Bean etc... as of yet i've not been able to use any of them.
Thanks for the continued response.
Ricky
THANK YOU
eakav said:
ok man, you've got the same problem like me
First thing, all roms that make your touch screen doesn't work will based on cm (e.g. cm10, slim, any jb).
and ALL STOCK roms will get no problem.
There's lot of people here got this problem and still has no clue why this problem occure to ours, so sad story.
Someone says that the touch screen firmware sould be updated to the lastest version, but i don't know how.
One solution that i found is, remove the battery to turn off then turn it on to reboot again and again. If you lucky enough, the touch screen will work like a miracle!
and the success rate is also <50% ( based on my experience only)
Click to expand...
Click to collapse
Ah ha... sounds like you have the same problem as me!
Did you manage to get any JB ROM working? If so, which one, just so I can try that also...
Does anyone else have an idea on how to update the touch screen firmware?
Really appreciate the feedback, thank you one and all!!
Ricky
ricky7D said:
Ah ha... sounds like you have the same problem as me!
Did you manage to get any JB ROM working? If so, which one, just so I can try that also...
Ricky
Click to expand...
Click to collapse
This solution is the one that i think it can move some files which related to touch screen.
http://forum.xda-developers.com/showpost.php?p=34593771&postcount=23
But sorry, it still get sometimes for the touch screen didn't response :crying:
However, as i mentioned above; you can get ALL jb rom working :fingers-crossed:
But depends on your luck. Just turn it off when the touch screen didn't response, then turn it on again (and again) untill it work.
I hoped that the new linux kernel will solve this...
No touch
eakav said:
This solution is the one that i think it can move some files which related to touch screen.
http://forum.xda-developers.com/showpost.php?p=34593771&postcount=23
But sorry, it still get sometimes for the touch screen didn't response :crying:
However, as i mentioned above; you can get ALL jb rom working :fingers-crossed:
But depends on your luck. Just turn it off when the touch screen didn't response, then turn it on again (and again) untill it work.
I hoped that the new linux kernel will solve this...
Click to expand...
Click to collapse
I have same issue have tried many stock based roms and kernels no problem but any CM based rom I have no touchscreen.
You can reboot and about 1 in 5 times it will work
Maybe it only affects certain versions of the phone. I even tried re-locking bootloader and doing official sony update then tried CM again I tried 7.1,9 and 10
same problem.
Here's where I am...
UPDATE:
So, here is where I am. Using advice from previous replies I have managed to install Xperia Ultimate HD and this is working off of the Lupus kernel without any issues. I'm still unable to get ANY Jelly Bean roms working...
Maybe my device will just not work on JB :crying:
Any other tips or tricks are greatly appreciated, would love to get JB working on here my beloved Arc S.
Ricky :good:
Any news here?
I have the same issue over here with a colleagues LT18i
I have same problem, touch screen doesn't work on many different kernels... only work on stock kernel
Any news about this problem?
Hi,
I am fairly new to rooting (infact this is my first post).So,please be gentle if i am violating any rules.
I had put JELLY BAM on my GNEX and it was running fine. I tried partitioning my memory which did not go well so then I tried reflashing my ROM , which again did not go well and accidentally i deleted my ROM and all of my backups. So basically I am not able to use my GNEX .
I have no ROM and was only able to access bootloader and recovery menu (TWRP) . So i tried flashing it thru NRT(by wugsfresh) and since then I am stuck in bootloop(Was trying to flash stock JDQ39) & upon that I am back to stock recovery of android. Also, now PC is not ready to detect my GNEX as ADB device.
Please help me out, I am in dire need of it. Cant find a simillar issue any where else.
Thanks in advance.
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
work in progress
Zepius said:
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Thanks for the prompt reply. Halfway thru ..
Zepius said:
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Nopes, still stuck in bootloop. Tried the tutorial twice now.
Also, earlier i was following the same procedure albeit from NRT.
Please suggest what is wrong with my phone and a possible solution
madforsoccer said:
Nopes, still stuck in bootloop. Tried the tutorial twice now.
Also, earlier i was following the same procedure albeit from NRT.
Please suggest what is wrong with my phone and a possible solution
Click to expand...
Click to collapse
put simply you probably trashed your partitions. you might have to use ODIN to repartition
madforsoccer said:
Nopes, still stuck in bootloop. Tried the tutorial twice now.
Also, earlier i was following the same procedure albeit from NRT.
Please suggest what is wrong with my phone and a possible solution
Click to expand...
Click to collapse
I had a similar problem. I thought it was because my disk was partitioned-screwed. So I tried this: http://forum.xda-developers.com/showthread.php?t=2065470
It didn't work for me, but it's worth a shot for you. Give it a go.
Will try the ODIN method.
Also, do you think I am experiencing persistent boot-looping because I wiped off my 'system' (did it for the first time)
coz i have been flashing ROM's and kernels on weekly basis now and this has never happened before.
Still not working, tried the ODIN part also, still stuck in boot-loop.
I jus want to know what exactly is the problem here..!!
getting frustrated now.
Hi all,
Since I am facing difficulties flashing ROM. IF only someone can share a backup image of ROM (CWM/TWRP) with me I can get it restored and flash another ROM later on as need be.
You said you partitioned your memory. What exactly do you mean by this, what did you do?
cupfulloflol said:
You said you partitioned your memory. What exactly do you mean by this, what did you do?
Click to expand...
Click to collapse
I was trying to implement swapper on my gnex , which when failed led to this mess i am in currently.
So like many, I took a stupid OTA on one of the roms (CleanROM) and got stuck in recovery boot loop. I tried all the methods I could find on xda but none worked. I then started reading all the way through threads and found the fix... wish they would update the original posts... so for those in this same predicament, here is how I fixed it so you don't have to read through everything.
so the FULL ADB method code looks like this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
exit
adb reboot
I of course take no responsibility if this doesn't work for you. I got the original and extra code in this thread http://forum.xda-developers.com/showthread.php?t=2451696 and all true credit goes to them. I'm simply putting ALL the information in the one original post of this thread in hopes of saving someone else a lot of time trying to find that extra line of code burried in the other thread.
I ended up doing this as well and now have my phone back. My problem now is that I have the notification of that update and I can't get it to go away.
DooLocsta said:
I ended up doing this as well and now have my phone back. My problem now is that I have the notification of that update and I can't get it to go away.
Click to expand...
Click to collapse
I personally switched to a ROM that was already based on the update. I haven't looked but I'm sure there is a way to turn them off.
DooLocsta said:
I ended up doing this as well and now have my phone back. My problem now is that I have the notification of that update and I can't get it to go away.
Click to expand...
Click to collapse
You can get rid of the notification by freezing the "Software Updater" app in Titanium Backup.
kuwlij said:
You can get rid of the notification by freezing the "Software Updater" app in Titanium Backup.
Click to expand...
Click to collapse
tried this didn't work? even wiped the data still have the icon.... Any other suggestions?
vegasdavek said:
I personally switched to a ROM that was already based on the update. I haven't looked but I'm sure there is a way to turn them off.
Click to expand...
Click to collapse
What ROM did you end up going with? Each time I try a ROM the WiFi calling does not work and in my area I have to use that more than I would like.
This is almost an exact repost of the other bootloop fix.
TheNetwork said:
This is almost an exact repost of the other bootloop fix.
Click to expand...
Click to collapse
Yup. This is a repost only. I have seen couple of Guides here in G2's thread.
Sent from my LG-D802 using XDA Premium 4 mobile app
TheNetwork said:
This is almost an exact repost of the other bootloop fix.
Click to expand...
Click to collapse
Agreed, which is why I said that the other thread is where I found the fix... but the original post in that thread didn't actually offer a fix when I got stuck in the loop. As a result I spent a lot of time trying other attempts to fix as well as combing through threads before finally finding the extra line of code to make it work.
So I posted a new thread so that someone else doesn't have to waste their time like I did trying to find a fix.
DooLocsta said:
What ROM did you end up going with? Each time I try a ROM the WiFi calling does not work and in my area I have to use that more than I would like.
Click to expand...
Click to collapse
I'm using this rom currently: http://forum.xda-developers.com/showthread.php?t=2595586 as I too need the WiFi Calling feature.
If you are on a T-mobile based rom, the way to 'freeze' the update is different than the others.
T-mobile roms use 'Google Services Framework' for the update, and obviously you can't freeze that app.
So, what you do is d/l a program called 'Autorun Manager'. Then inside that program, scroll down to 'Google Services Framework' and disable 1 receiver.
The one you want to disable is called 'com.google.gsf.update.SytemUpdateService$Receiver' Just disable that (by unchecking it) and then reboot. You will not receive a notification to update ever again.
Also, go into the folder /cache and delete the FOTA d/l. You will need R/W permissions in the root directory to do this. So use whichever file manager you prefer for that.
The FOTA d/l is easy to spot, it's a 150mb approximately zip file with a bunch of chars and should be the only file in that directory. There are a few folders as well, but, ignore them and just delete the 1 file.
I'm in the same situation - reverted back to stock rooted with twrp recovery and now boot back to recovery. I haven's used adb much, but do know how to open the cmd window in the adb directory on my computer and it appears I'm connected to my d800. However, when I run the adb devices command I see the device code and recovery listed. When I type the first line of the code in the first post, adb shell, I get ~ # ←[6n and can't type in any additional commands.
Am I missing a step - or just not understanding the process??
UPDATE - Nevermind - I just typed in the command dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota using TWRP's Terminal Command and the phone booted right up to Clean Rom.
Thanks vegasdavek for your repost on this fix!
vegasdavek said:
So like many, I took a stupid OTA on one of the roms (CleanROM) and got stuck in recovery boot loop...
original post of this thread in hopes of saving someone else a lot of time trying to find that extra line of code burried in the other thread.
Click to expand...
Click to collapse
Thanks, found this now, only after I already fixed my issue, but this is useful. Perhaps you should also update it to reflect it can be done with the Terminal in TWRP..