Develop Bugs

[Q] Problem with Rom: RevolutioN 1.7

OK, so I am not new to the xda desire scene,
(Despite the fact that I can't post in the rom development thread regarding this issue)
I have tried installing this Rom in as many different ways as I can over the past 3 hours:
Using EXT3 rather that EXT4
Changing Hboots
Making sure that I have got the correct download (a2sd+/D++)
Wiping a billion times over
etc etc.
HOWEVER no matter what I do I cannot get this Rom to function
When I boot up for the first time, I just get a wallpaper and notification bar.
No touch screen response/button response.
Only the power button works as a method of turning the screen on/off
I assume from experience at this point in first boot HTC's setup program
(or whatever it is) should start and guide me through
linking up accounts/inputting Wifi keys etc.
I have scoured the rom thread and others regarding rom problems and nobody seems to have had this problem of the Setup manager not starting.
As nice as the Gingerbread Screen On/Off animation is I would prefer to do abit more with my phone
I hope I have posted in the right section and I would very much appreciate it if anyone who has had this experience could help me fix this problem and get a working phone...
(ps. The Rom looks very good, if only I could get it working)

First of all try to redownload the rom!!!

And double check the md5
Swyped from my CM7.1 Desire using XDA Premium App

timmaaa said:
And double check the md5
Swyped from my CM7.1 Desire using XDA Premium App
Click to expand...
Click to collapse
halaros2 said:
First of all try to redownload the rom!!!
Click to expand...
Click to collapse
Hey Thanks guys, but..... I re-downloaded the ROM both versions 1.5 and 1.7 (since 1.5 is thought to be more stable) :/ and get stuck at exactly the same place :SSS I'm am abit baffled since I change Rom's alot and have never experienced this before

Did you wipe dalvik? btw your sd card partion need to be at least 1 gigabyte. It worked for me i had same issue as you. First post on XDA

My first installation of 1.7 didnt work and I had to pull the battery and I thought the same thing was happening with my second try, as the screen just went blank after all the crazy changing shapes that happen during boot. However once I touched the power button the setup menu appeared.
I thought this was strange as every other ROM I have tried went straight from the boot animation to the phone starting without the screen blanking out. I know this doesn't help solve your problem but it might mean something to somebody else, who can then help you further.
ps I have been running the ROM for the past week and I haven't had a screen freeze yet. Which has been a revelation for me, as every other ROM ive tried has been really bad for this.

Elocity a7+

i was trying to install gingerbread on my elocity a7+ tablet and it seemed to be going fine. It said i needed to reboot to continue so i did. When i restarted it, it never started into an os. I turned on straight to a black screen, no text at all. I've tried holding all the key buttons and even unplugged the battery. Nothing works. How can I fix this? Installing a custom ROM or going back to the factory would be fine.

Having this exact same problem, I was trying to install the android market mod. Everything was going fine, then this.
I think we've bricked our tablets. All the mods I saw were for the A7, not the A7+. I read that there were no software changes between the two, and figured the same mods should work.
I would appreciate a more informed opinion, though.

Mine comes today. Did you just try to apply the 1.42 mod or gingerbread. Please be more specific. This thing is going back if I can't mod. Thanks.

I tried the 1.42 mod. Thread creator tried gingerbread. They both caused the same outcome.
It seems like it's installing fine, but then when it reboots, you get the black screen.

Wow that sucks, but I really appreciate your post. The device will be at my door in the next couple hours. Now I have to decide if the device is worth the cost ($199) without the mod. I guess with sideloading it won't be too bad..... Thanks again

It's a very nice tablet, if all you want to do is use the internet with it. You need the android market to get the best apps, though. Without that, it's useless, in my opinion. I'd rather just use my real computer.

Hopefully Dexter will get his hands on one and it's just a small change in the rom..... Not sure which way I'll go.... probably return

Yeah, but seriously. Anybody out there have any ideas? The system seems to be failing to boot entirely.

HoratioGiovanni said:
Yeah, but seriously. Anybody out there have any ideas? The system seems to be failing to boot entirely.
Click to expand...
Click to collapse
Tried going back to stock? Can you mount it in Windows?
http://elocitynow.com/prod_a7-plus_downloads.shtml

If you made a mistake and installed A7 stuff on the A7+ here is a link to the instructions to fix it.
http://elocitynow.com/downloads/restoring-the-A7-plus-from-pc.pdf
Dan

Help! Phone not bricked, but won't boot.

Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?

Try flashing the stock tar in odin if nothing else works.

DroidGnome said:
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Click to expand...
Click to collapse
Just flash the stock tar ur downloading in Odin. Ur fine even if you managed to Bork recovery as long as u can still get into dl mode ur ok

I've haven't seen this problem on the Sprint variant yet but it definitly sounds like it's fixable
Like others have pointed out, since you can get into Download mode fine flash the Stock Odin tar file found here
When you boot up I would consider doing a data wipe (Factory Reset option in Settings>Back up and reset) but that's up to you

Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure

DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium

DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
Ya Ive seen some build.prop changes mess things up. Luckily you could get back up.
Fun feeling huh! lol

fergie716 said:
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store

DroidGnome said:
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
Click to expand...
Click to collapse
Glad to hear you're up and running again!!
Best excuse ever to Sprint is when I woke up it was like that haha

[Q] Boot hang after flashing using Odin back to stock rooted

Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Another Update:
I just re-flashed with odin, this time it says it successfully completed but once again it's stuck at the flashing Samsung logo with the indicator led on.... I am starting to really freak out lol. I have another file downloading that is supposedly just stock, no root or anything...

rakhov said:
Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Click to expand...
Click to collapse
Actually have the exact same situation going on right now, I will post if I can find a fix. Downloading an alternate stock build I found now and will let you know how it goes.

Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!

rakhov said:
Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!
Click to expand...
Click to collapse
Thats exactly what Odin is working on loading now, Download had just finished.

avarize said:
Thats exactly what Odin is working on loading now, Download had just finished.
Click to expand...
Click to collapse
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD

rakhov said:
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD
Click to expand...
Click to collapse
I've always noticed the LED being on during boot (or some of the boot) and it was also on when I had a bootloop during cm9 so I don't think it means anything.

Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.

rakhov said:
Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.
Click to expand...
Click to collapse
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
Click to expand...
Click to collapse
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 for reboot options to force it into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.

avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 to force into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.
Click to expand...
Click to collapse
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.

rakhov said:
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.
Click to expand...
Click to collapse
Should have explained a bit better. Yes that toolkit
While it was stuck at samsung screen.
1 For AT&T (Obviously)
20 For reboot options
1 For recovery.
Then wipe data/cache
Then wiped cache (no idea why)
then rebooted.

When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium

That is exelent. I am downloading the toolkit right now and will report back shortly.
Once you got it to boot, did you still have root? I am wondering if you flashing the "stock rom" that I posted, if that had any impact. I have only pushed the root66 file, so I am expecting root when(if XD) I get this thing going again. I appreciate you being more thorough with your instructions, and will report back with my results as soon as I get some
Also, are we loners on this? I am not seeing any other posts about going back to stock/stock rooted from modded roms using odin? I am trying to figure out the best method to go back to stock. I made a nandroid and I am sure that would work, but all of this word about having to flash different kernels and bluetooth/wifi drivers to get stock working properly makes me wonder if just using odin is the easiest method, as it restores everything on the phone (to my knowledge).

crash822 said:
When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
That is great, this may sound a little silly, but how do I boot to recovery? Thanks!
UPDATE:Nvm, google hehe. I just did the factory reset...Things are looking good so far, the haptic lights turned on at least...BOOM! We are good gentlemen. It looks like all it took was the recovery wipe. This is great news! I will try to figure out how to mark this as solved, and you crash822, you get a thanks

NP sir. We all have to start somewhere. Luckily for me I was already planning on doing a full wipe so I backed up everything I wanted to keep from my phone onto my computer before using odin.

I seem to be having the same issue. I've downloaded the toolkit as you guys have suggested. are you guys in download mode on the phone while you use this? it seems to want me to be in debugging mode and i can't get to that. I've tried a factory reset with no luck.

[Q] Did I really just brick my phone by changing a setting? What now?

I have been using smart keyboard pro for a long time now, and love it. But yesterday I turned on swiftkey, because I bought that once at a sale. I tried it for a day but didn't like it. So I wanted to change back, now here it went wrong.
I went to the settings and saw stock keyboard = swiftkey. I unchecked swiftkey from the usable options but the stock keyboard stayed the same. So then I wanted to change the stock to smart keyboard, and it crashes. My phone rebooted a bunch of times. Now when I pull the battery, it boots, goes to the lock screen, which I can unlock if I'm fast, but then it reboots again. What do I do now? I don't have enough time to get to the settings. I really don't want to do a hard reset for something stupid like this..

Did you try to get to a recovery and wipe cache and dalvik? Don't know if that might help, but it's worth a try. You could also just reflash your existing ROM in CWM.

I don't have recovery. I might flash the stock rom again maybe that helps.. But there's no way to somehow delete apps from the phone in download mode or something?

Yes you could pull the keyboard apk from the phone. You have to use ADB shell.. If you dont know how to, id suggest doing abit of research..
When pulling APK's via ADB you need to know the exact spelling an case i.e. adb pull Phone.apk
You will also have to type where the file is located on the Phone and then where you wish to save the pulled files..
http://android-dls.com/wiki/index.php?title=ADB

Just reinstall the rom I had that problem and it was sorted I had it on the sg 3
Sent from my Samsung Galaxy Note II using TapaTalk 2.

eXplosion17 said:
Just reinstall the rom I had that problem and it was sorted I had it on the sg 3
Sent from my Samsung Galaxy Note II using TapaTalk 2.
Click to expand...
Click to collapse
Lol I got a email with your original reply, so you can't hide your fail but thanks for the advice.