Hi. I'm still too new to post in the Dev forum.
If Th3Bill happens to see this, I've been having issues with his ROMs since they've been using Aroma.
I was on CWM but changed to TWRP. That didn't help.
I've tried PA & CNA. Both don't install the extra programs and usually I can't get past the setup screen. I just get a black screen. If I pull the battery and reboot, it starts and the screen goes black instead of lock screen. I hear emails or messages notifications but can't do anything.
Anyone with ideas?
peatee said:
Hi. I'm still too new to post in the Dev forum.
If Th3Bill happens to see this, I've been having issues with his ROMs since they've been using Aroma.
I was on CWM but changed to TWRP. That didn't help.
I've tried PA & CNA. Both don't install the extra programs and usually I can't get past the setup screen. I just get a black screen. If I pull the battery and reboot, it starts and the screen goes black instead of lock screen. I hear emails or messages notifications but can't do anything.
Anyone with ideas?
Click to expand...
Click to collapse
You should probably post in his thread for the ROM you're having issues with. He's more likely to answer that way.
Thanks but I can't.
The forum keeps telling me that I don't have enough posts to do anything in the Dev forum.
Did you wipe before starting aroma? If so, don't. Also using cwm recovery you need to go to advanced>show error>save log>reboot recovery. Twrp doesn't have that option. I was only able to install cna after going back to cwm from twrp then the above steps. Hth
I had some issues with paranoid .. make some BS posts till you can post in dev section or PM him he might be able to help
Random Canadian said:
make some BS posts till you can post in dev section
Click to expand...
Click to collapse
That's a REALLY horrible advice and will only get you in trouble.
peatee said:
Hi. I'm still too new to post in the Dev forum.
If Th3Bill happens to see this, I've been having issues with his ROMs since they've been using Aroma.
I was on CWM but changed to TWRP. That didn't help.
I've tried PA & CNA. Both don't install the extra programs and usually I can't get past the setup screen. I just get a black screen. If I pull the battery and reboot, it starts and the screen goes black instead of lock screen. I hear emails or messages notifications but can't do anything.
Anyone with ideas?
Click to expand...
Click to collapse
I had this same issue with the latest PA. I had a black screen, but was somehow taken to the play store, where my apps were downloading/updating. So it seemed to be only the launcher that wasn't working. I also rebooted without success. Then I booted into recovery and wiped cache and dalvik and fixed permissions, rebooted -and it worked!
Sendt fra min MB860 med Tapatalk2
peatee said:
Hi. I'm still too new to post in the Dev forum.
If Th3Bill happens to see this, I've been having issues with his ROMs since they've been using Aroma.
I was on CWM but changed to TWRP. That didn't help.
I've tried PA & CNA. Both don't install the extra programs and usually I can't get past the setup screen. I just get a black screen. If I pull the battery and reboot, it starts and the screen goes black instead of lock screen. I hear emails or messages notifications but can't do anything.
Anyone with ideas?
Click to expand...
Click to collapse
Try my rom Androbreadcrumbs, I also used the aroma installer and it worse flawlessly whether you do wipe or dont before, it does everything for you. See if that works, I personally tested the entire installation from beginning to end for 2 weeks in development before posting it online so there are no bugs with the installer whatsover, if you still have issues after using my installer, then scream at me in PM, i'll help you out
P.S. Th3Bill also doesn't have an atrix and has a photon himself so he cannot test everything for our phones but he gets most of the things on point as he handle the MIUI builds for 12 different devices I believe, not to mention the other half-dozen ports that he does of other roms to other phones. So he has a lot on his plate to deal with, but if you can get a logcat off your phone using "adb logcat" and dump it into a .txt file so you can send it to him, you can still shoot him a PM with it and more than likely he will work with you to help out with whatever the issue is, he'll work with you if you help him to help you by providing such things as a logcat and full details on your configuration in Aroma & which choices you chose and what the problem is that you're experiencing. Remember, always goto the horse's mouth before going to the horse's ass and making an entire thread about something like this. For all you know, shooting him a proper PM could've resolved your problem faster than making a thread about it. Just saying pal, not trying to be an a**hole.
I believe its posted somewhere that you must fix permissions after flashing.
Sent from my MB860 using xda premium
Never heard of that, the updater-script should set all the required permissions for you. The whole idea behind using aroma is to make the user not have to do anything but choose whichever options he\she may want to install and thats it. The rest should be handled by aroma config script and updater-script so the user has to do nothing more than reboot after installation and enjoy the experience. I've done extensive research on the edify syntax script writing for the updater script and the syntax for connecting the aroma-config file installer script and have never read anything about setting permissions afterwards anywhere after using aroma.
But feel free to read up yourself and perhaps I may have missed something somewhere. These thread should point you in the right direction.
Aroma, Edify, updater script FAQ
Introduction to Edify & Explanation of syntax
Original post by amarullz who created aroma & detailed structure breakdown of how it works
amarullz's website for aroma rom manifestation
pre4speed said:
Did you wipe before starting aroma? If so, don't. Also using cwm recovery you need to go to advanced>show error>save log>reboot recovery. Twrp doesn't have that option. I was only able to install cna after going back to cwm from twrp then the above steps. Hth
Click to expand...
Click to collapse
I believe wiping beforehand won't bug out an installation, but merely be a redundant step, since the installer will perform a wipe anyway.
Thanks for all your comments.
My intention is to post in the proper thread but I cannot yet. (as I stated originally) I also didn't want to bother him yet with PMs. I'll take some of your suggestions and see what I can figure out.
Thanks for taking the time to post your thoughts.
Hey, if you downloaded his rom then by all means you can shoot him a PM asking for a suggestion on what you should do. If your intention was to post in the right section, then making this thread in the Development section is a big no no and is the reason why you cannot post in that section until you atleast have 10 basic posts under your belt so you understand where you can post such topics.
Unless you meant that you were going to post in the thread for which ever rom you downloaded, then thats cool but you don't need to wait to be able to get send the developer a PM to ask a question. We're people too and majority of the developers on here wouldn't mind helping someone out with a problem they're having trying to get their rom working.
Long as you help the developer to help you by providing something that can be looked at like a logcat log for example instead of just saying something like "i installed everything, restarted but it gets stuck at the M logo and doesn't boot, help please".
Try running the installation again, after it's finished, reboot the phone and see if it boots again. If it doesn't boot up again, connect the phone to a usb cable to the PC, boot into recovery again, then open up a command prompt and run ADB, check that you can communicate with the phone by typing in "adb devices" and you should see a serial number and the word recovery listed which would be your phone. Then type in
Code:
adb logcat > "logcat.txt"
That will dump the device logcat into the logcat.txt which will be located in the same directory as where you are running adb.exe from, then post it up here for people to take a look at and see what's failing
android-DEP said:
Hey, if you downloaded his rom then by all means you can shoot him a PM asking for a suggestion on what you should do. If your intention was to post in the right section, then making this thread in the Development section is a big no no and is the reason why you cannot post in that section until you atleast have 10 basic posts under your belt so you understand where you can post such topics.
Unless you meant that you were going to post in the thread for which ever rom you downloaded, then thats cool but you don't need to wait to be able to get send the developer a PM to ask a question. We're people too and majority of the developers on here wouldn't mind helping someone out with a problem they're having trying to get their rom working.
Long as you help the developer to help you by providing something that can be looked at like a logcat log for example instead of just saying something like "i installed everything, restarted but it gets stuck at the M logo and doesn't boot, help please".
Try running the installation again, after it's finished, reboot the phone and see if it boots again. If it doesn't boot up again, connect the phone to a usb cable to the PC, boot into recovery again, then open up a command prompt and run ADB, check that you can communicate with the phone by typing in "adb devices" and you should see a serial number and the word recovery listed which would be your phone. Then type in
Code:
adb logcat > "logcat.txt"
That will dump the device logcat into the logcat.txt which will be located in the same directory as where you are running adb.exe from, then post it up here for people to take a look at and see what's failing
Click to expand...
Click to collapse
Thanks android-DEP ...
I did end up PMing him and I'll follow your steps to get the logcat to him. My intention was to post my issue in the thread for the specific ROM I got the error with. I was not trying to open a new random post with my issue in the Dev forum. I've been around forums enough to know that would be a big no-no.
Thank you again.
Well then, now that you put it like that, I can respect that. Some people come on here aimlessly and post garbage or truly stupid questions in the development section without using simple common sense to try to find a solution to their issue. Then disappear after the original post and never respond or post anything ever again. Not a big deal but gets annoying after a while as it's completely pointless and all the minutes other people spend reading the dumb posts, can never be regained back.
As you can tell this forum is moderated and kept up clean as well as the section topics are strictly followed when it comes to posting threads. So since you know how the forum thing works, it will only help you gain the most out of being on this one and welcome aboard.
Don't hold back on shooting any developer a PM if there's no other way you can contact him and run into issues using his rom. It's your right if anything to be able to contact the developer when you run into problems that aren't common or can easily be resolved otherwise.
Th3Bill is doesn't have an Atrix himself, he has a Photon. Although most of the things are really similar or identical between the 2 devices, he is not able to physically test the Atrix builds he put out and he relies on people to help him troubleshoot any Atrix builds. So the more info you can bring to him about anything problem you run into with the Atrix, the more detail he has to be able to debug the issue and correct it.
So it's better to raise the issue to his notice so he can look into it and correct it before release the next build which could potentially carry over the bug which would make it even harder to troubleshoot.
Related
Can't receive phone calls. Just shows up in missed call log. No ringing.
An answer would be easier to obtain with more information.
Sent from my Eris using XDA App
It would be very helpful if you would consolidate all your issues into one of your post, as they may be connected, and included more information. Usually the basics needed are atleast which ROM you are using, what changes have been recently made, and a detailed description of the problem.
I put vanilla cynogen mod rom on. And now it wont get calls when. Someone. Calls me it just shows up as missed call in call log.
I'm not trying to be an asshole, but I would just like to impress upon you how perfectly useless you have been to yourself. Vanilla Cyanogen Mod ROM, really, which one, there is no "official" CM for Eris, so which port are you using. If it's showing up in your missed call log, the call reached your phone, missed calls due to no service, airplane mode, phone shut off or any reason except they were simply not answered, do not show up in the missed call log. If it's in the call log you can almost certainly receive calls, your notifications may not be working. Have someone call the phone while you are watching it, if the display does not indicate an incoming call then you do have a novel problem. Try this and please report.
Sorry for the lack of knowledge on this I'm just having alot of problems with it and don't know where to start. My friend introduced me to rooting n different Rome on his phone n said to try it out. So sorry. I tried someone calling me and no display of them calling then I checked call log when they hung up n it showed a missed call. If that. Helps any.
I have modle. Number- froshedyo. Android version-2.2.1. Kernel version-2.6.29-decafuctcfs-dirty-c6271491. Mod version-froshedyo-6.2-rci-desierc. Build number-frf91
If that helps
lol "if that helps," dude that exactly what you've been asked for in each of your threads, I'll do some tinkering, see if I can find you a way to get Amon-RA Recovery without too much hassle, that can help resolve most of your issues I've read about. I'll post back later tonight.
Alright! Thank you so much. I know I'm a retard.
BTW what method did you use to root the phone, a direct link to the tutorial or the name of the app, whatever you used, please.
One click root
joejoemotorcycle said:
One click root
Click to expand...
Click to collapse
Well, before I get too far into this, One Click Root (jcase's I presume) installs Amon RA Recovery, RomManager doesn't actually install ClockWorkMod Recovery, it's a sort of one time run overtop of Amon, try booting into recovery directly.
Turn the phone completely off, Press and Hold the VolumeUP key while Pressing and Holding the Power/EndCall button. Alternatively, with the phone on Press Power/EndCall, chose reboot, recovery, ok.
If you have a menu with several options in green text that you highlight with the trackball you are in Amon, and this will be easy.
Yup it's in green using trackball.
Outstanding, read this first post very carefully and follow it step by step, if you want to try FroShedYo again, make sure to re-read this first post entirely. The reason you did not have market was because you did not flash this file. If you want to start over completely from stock you may also use bftbo's FlashBack21
While you are in Amon Recovery, connect your phone to the computer with the USB/Charging cable, select the "USB-MS toggle" option in Amon, press the trackball. On your computer find the phone, transfer whatever ROM you wish to flash to the SD Card, do not place it in any folders. Follow step by step the instructions here. If you are flashing FroShedYo, (or any CM ROM that requires a gapps flash) after you Flash the ROM, but before you reboot, flash gapps.
Make sure you understand all of the instructions before you do anything, if something is unclear feel free to ask.
Alot of this stuff can get overwhelming if your new to it, I bricked the first phone I rooted because I wasn't paying attention, but be cautious, and be sure you understand anything new you want to do to your phone.
USSENTERNCC1701E said:
If you have a menu with several options in green text that you highlight with the trackball you are in Amon, and this will be easy.
Click to expand...
Click to collapse
BTW this is based on the assumption that you "flashed" ClockWork Mod Recovery from RomManager, both Recoveries use this same styling. The procedures are also very similar for both, as long as you have a custom recovery you should be able to fix this. Amon is "preferable" for the reasons bftbo brought up in another of your threads. To definitively tell which Recovery you are using look for white lettering on the bottom of the screen,
Amon-RA Recvoery - Build : RA-eris-v*.*.*
ROM Manager - ClockworkMod Recovery v*.*.*.*
It says build : eris-v***
Did you have any luck reflashing the ROM with a full wipe?
joejoemotorcycle said:
It says build : eris-v***
Click to expand...
Click to collapse
Apologies for butting in.
Amon_RA should look like this: http://i756.photobucket.com/albums/xx209/erisuser1/Amon_RA_stuff/Main_Menu.jpg
FWIW, there is a mini-tutorial with lots of pictures (of the Amon_RA menus) in this post on AF
Now, back to the regularly scheduled programming.
Yeah, I googled and couldn't find anywhere a build : eris-v*** So I'm kinda banking on a bit of oversight or a typo. That pic is very handy, much more specific than "menu with several options in green text" lol
Thanks bftbo
Yes did everything u wrote n put gapp. In n flashed all n seems to be working awesome. Thank you so much. If I have any issues then I will repost. Thanks again
Help Needed, I am, lost!
Ok, first things first, I am now on version 1.2.4349 of what I am not sure. I think it is a factory ROM.
I restored from a bricked device, using nvflash and the update Rom 1.2.4349. Since I have been trying to install Clockmod. I can't get it to work.
Every time I boot per instructions here, nothing happens...either it freezes on the first screen with the birds, showing update kernel found.. or it starts the update then freezes. I have tried internal boot file and external boot file... even tried clockmod v8. with same results.
There are so many post about rooting this device and do's and don'ts that now I have become confused.
Can someone please point me in the right direction. I want full market access, and a workable rook. Where do I need to start?
Thanks
This will get you going in the right direction.
http://viewsonic-gtablet-for-dummies.webs.com/
ok, I must not be your average dummy. I followed directions to the word. Trying to install Clock work mod via option three(3) nvflash. Everything goes well... flash runs and does what it should. I only saw a brief blimp of a dos window when it ran. Next tried to boot using power and v+.... It said "Recovery key detected", I released buttons...now it says "booting recovery kernel image." And it just sits there, is still there now while I type this post.
When I looked at the version it says I am on version 1.2.4349, so I used the 1.2 side of the chart.. Could I have it all clogged up from all the prior failed attempts.
thanks for any help
The "dos window" should stay up for a minute or two. Are you sure your initiating the nvflash correctly? I think it's something like "nvflash.bat"
the dos window was only a flash, and the instructions said less than a second, and you might not even see it.. I used "nvflash_gtablet.bat" to start the flash.
I am lost still
It looks like you've selected the "flash clockwork with nvflash." This requires that you already be on a custom rom, which I don't believe you are.
There is a full nvflash available which will install clockwork AND completely wipes your tablet back to stock. (an excellent baseline to flash a new ROM)
This is the correct tutorial.
http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm
You'll want to use the 1.2 version with clockwork.
After that, I recommend the Flashback ROM if you're looking for Honeycomb. That ROM includes a text file with a very literal step by step process for installing the ROM. It will walk you through partitioning your SD Card (which is important) and flashing the ROM.
for helping out a noob that didn't thank you, brett.
I thank you for 'im.
If I may say so, I am sorry I can't be on 24/7 and only now have reviewed this post.
Thank you for thanking brett, for me, but there was no need, Because I can and do and will thank all for all they do in this forum. If you care to look at any of my post you will see I do thank everyone.
lasersc said:
If I may say so, I am sorry I can't be on 24/7 and only now have reviewed this post.
Thank you for thanking brett, for me, but there was no need, Because I can and do and will thank all for all they do in this forum. If you care to look at any of my post you will see I do thank everyone.
Click to expand...
Click to collapse
it's okay, laser. nbd. I did it half jokingly. Usually courteous to thank people that help you out...
lasersc said:
thanks for any help
Click to expand...
Click to collapse
Your all good lasersc
Happy to contribute qkster, I'm not quite advanced enough to troubleshoot most problems, so I like to jump on the easier ones when they go otherwise unnoticed.
brettdwagner said:
Your all good lasersc
Happy to contribute qkster, I'm not quite advanced enough to troubleshoot most problems, so I like to jump on the easier ones when they go otherwise unnoticed.
Click to expand...
Click to collapse
You gave good advice, brett.
On the flashback update thread, there is a recovery package.
Included in the package is easy step by step instructions that spells out everything that you need to follow to nvflash and flashing.
I refer to that frequently.
I hope laser was able to go thru that package.
.39 kernel is almost done. HC 3.2 or ICS is just around the corner.
You rock Brett, Thank you so much. I did as you suggested this morning and everything went well. If you only knew, how long I have been fighting this deal, but with your couple of post...Everything is Well
Thank you again!!!
Which is the best rom to go with?
I've downloaded _n0p_'s DSC v0.7 and Tenorntex's Longhorn 2.1 v2, seeing as these 2 were the newest and latest and had Android 2.3.3
Are there any other better rom's or has anyone tried the 2 I listed, if so whats the difference?
Thanks
Better is very vague when it comes to ROM's it all depends on what you want in a Rom. I have old Simple Streak 1.2. Yes there is newer ROM's out but this one works perfect for what I need. In my Case Stability.
DSC is the most actively developed/supported. Plenty stable for me. I don't think any of the earlier Froyo based ROMs are being developed further.
I meant as far as Stability, Performance and up to date, I don't care about the Stage UI and was gunna theme it myself or use SPB Shell 3D.
Could someone point me in the direction to an easy install rom?
I don't wanna install "these update pkg's" after renaming and then plug my phone into the pc and open cmd and then type this in on the pc. et cetera et cetera
I just wanna download a zip drag it to the card, bootup in safemode and install from sd card.
I'd consider doing all that work if I weren't testing out the device.
I won it off ebay, the guy replaced the screen and said it's been randomly rebooting ever since. But he never did a factory reset or new rom install ever since fixing the screen, so I just wanna simply install a rom and see if it works then go on from there.
Any help would be greatly appreciated.
n1nj4Lo said:
Could someone point me in the direction to an easy install rom?
I don't wanna install "these update pkg's" after renaming and then plug my phone into the pc and open cmd and then type this in on the pc. et cetera et cetera
I just wanna download a zip drag it to the card, bootup in safemode and install from sd card.
I'd consider doing all that work if I weren't testing out the device.
I won it off ebay, the guy replaced the screen and said it's been randomly rebooting ever since. But he never did a factory reset or new rom install ever since fixing the screen, so I just wanna simply install a rom and see if it works then go on from there.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Unfortunately I do not believe that anyone can change the way that the Streak works just so it is more convenient for you or so that you don't have to learn anything.
In the time you took to navigate to XDA and make your post you could have flashed a ROM onto your Streak - plugging it in and everything.
The only ROM you can install by just putting it on the SD Card is the same one that is currently on the Streak, if you don't mind holding down a couple of buttons and using recovery mode.
n1nj4Lo said:
Could someone point me in the direction to an easy install rom?
I don't wanna install "these update pkg's" after renaming and then plug my phone into the pc and open cmd and then type this in on the pc. et cetera et cetera
I just wanna download a zip drag it to the card, bootup in safemode and install from sd card.
I'd consider doing all that work if I weren't testing out the device.
I won it off ebay, the guy replaced the screen and said it's been randomly rebooting ever since. But he never did a factory reset or new rom install ever since fixing the screen, so I just wanna simply install a rom and see if it works then go on from there.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
If anyone is wondering why developers leave and give the site a bad reputation look no further. Someone with over 600 posts under his username should not be making noob posts like this one. With so many posts he knows how to use the search engine and the wiki, but I guess when it comes to our device using the search engine and the wiki is an inconvenience, along with renaming a file "update.pkg".
marvin02 said:
Unfortunately I do not believe that anyone can change the way that the Streak works just so it is more convenient for you or so that you don't have to learn anything.
In the time you took to navigate to XDA and make your post you could have flashed a ROM onto your Streak - plugging it in and everything.
The only ROM you can install by just putting it on the SD Card is the same one that is currently on the Streak, if you don't mind holding down a couple of buttons and using recovery mode.
Click to expand...
Click to collapse
So would that be this: Streak_407_20707_14.pkg ? According to the first post above me do I rename it?
Strephon Alkhalikoi said:
If anyone is wondering why developers leave and give the site a bad reputation look no further. Someone with over 600 posts under his username should not be making noob posts like this one. With so many posts he knows how to use the search engine and the wiki, but I guess when it comes to our device using the search engine and the wiki is an inconvenience, along with renaming a file "update.pkg".
Click to expand...
Click to collapse
Some people learn better through interaction where they can actually ask questions... I don't have over 600 posts so who are you talking about? Furthermore if you are talking about first thing I'd do is learn how to read mr wise guy, secondly!! You tell me how one is supposed to learn which rom is the best based on user reviews and opinions, where do I go to find that out and wheres the wiki on that, unless you expect people to read 200 and 300 page threads also? I have barely 150 posts and rarely post at all unless it is to ask questions or make requests. It's not like I have 600 posts and every single one of them are questions.
This is only my second time dealing with android and second time flashing android first time it was simply moving a zip to the sdcard and booting up into safe mode and selecting update through sdcard, so certainly I'd be baffled and have questions when one time it was so easy and the second time I've gotta jump through hoops and everything.
Lastly since WHEN Is asking a Question SOOOO wrong in the Dell Streak 5 Q&A Category???? It's not like I posted it in the wrong area or something, but ohhh no'es how dare n00b be confused and need a lil help/guidance of some experienced users, ohh mercy me the drama in that!!
Last time I checked that is what XDA is here for, for people to learn, not to be attacked by asshat trolls like you.
If anyone is wondering why XDA has a multitude more lurkers than posters look no further than to the hardass that is Strephon Alkhalikoi View Postwho can't stand to see a n00b in need of help!
Like this
Flashing/Updating
Installing a recovery
Download appropriate recovery to flash from Stock Recoveries or Custom recoveries
Enter fastboot mode on your phone
Flash recovery with fastboot: fastboot flash recovery <path to recovery.img>
After flashing is complete: fastboot reboot to reboot
Finished
If you are using a custom recovery see Disabling recovery overwrite in stock roms and follow the steps there to prevent the Streak from over writing the recovery. Re-install your custom recovery after following those steps.
Click to expand...
Click to collapse
BUT THE VERY FIRST THING THE WIKI SAYS IS To Stay AWAY From Fastboot, but this tells you to use Fastboot... So what gives and which is it? LoL
n1nj4Lo said:
. . . .
Like thisBUT THE VERY FIRST THING THE WIKI SAYS IS To Stay AWAY From Fastboot, but this tells you to use Fastboot... So what gives and which is it? LoL
Click to expand...
Click to collapse
I hope that you can actually read better than that. The wiki does not say to stay away from fastboot. It clearly states two commands that should not be used on the Streak. It goes onto give a number of examples of using fastboot.
I hope that you other 157 posts (as I wtite this) on XDA were not as tiresome or ill-informed as the ones you have posted here.
The information you need is here in the forums, available at the links in my signature, and on other forums. Please exercise some patience and read the info.
marvin02 said:
I hope that you can actually read better than that. The wiki does not say to stay away from fastboot. It clearly states two commands that should not be used on the Streak. It goes onto give a number of examples of using fastboot.
I hope that you other 157 posts (as I wtite this) on XDA were not as tiresome or ill-informed as the ones you have posted here.
The information you need is here in the forums, available at the links in my signature, and on other forums. Please exercise some patience and read the info.
Click to expand...
Click to collapse
Uhh yea sory... I forgot about the 2 options to stay away from, just the dangerous part stayed with me. LoL
Do I need to be at a certain android version or can I make a semi-major update leap?
Also it says
Installing a stock rom
Reinstalling a stock rom will wipe all data!
1. Download stock rom pkg and recovery to install
2. Copy pkg to sdcard and rename to update.pkg
3. Install matching stock recovery
4. Enter recovery mode
5. After recovery loads press Camera to begin process
6. Finished
Click to expand...
Click to collapse
Do I need the recovery.img as well? It said nothing about a img file or anything just said "matching stock recovery" so yea, is that the right thing?
_
First I'm gunna try factory reset and see if that fixes the random reboot problem, hopefully it does the seller said he just installed the new screen and never did anything except for just trying to powering it up, use normally and it would reboot suddenly.
WELL NO DUH, you need to restore everything back to default settings with a factory/hard reset. Thats like trying to install a video card or webcam and expecting it to work right away without installing the dirvers. - Hopefully!
Well it's only getting as far as the dell logo screen/splash screen. I've tried the entering safe mode but nothing yet, once it's powered on it just sits at that screen.
dsc is great and very stable if you dont mind the few following quirks.
1. google maps will always run in the background unless you freeze it. This will drain your battery quite quickly
2. Wifi might or might not be broken, if it is broken use wifi analyzer if not profit
the benefits of dsc?
fast
running GB instead of froyo
dpi change is awesome.
screen default orientation is awesome
stable other than those few bugs
Battery life was decent.
-------------
Im however just running 2.2 froyo on a stock rogers. The battery life is amazing on stock 2.2 (a whole day, and still have about 30% with heavy usage and constant 3g) and the wifi works fine. For me this is the most stable rom however it is a bit slow compared to DSC. This phone is used for work so it has to just.. work.
---------------
Havent really tried the other roms yet, but depending on what you want out of the phone you can try the DSC and see if you can live with these little quirks.
Yea I was leaning more towards DSC than Longhorn, it looks like it's updated more frequently too.
Bad & Good News
Turns out when the guy replaced the screen he fried the mobo... Me and a friend at a small local pc store tried everything from rooting with new rom to factory resets. Always had the same problem.
But the guy at the pc store sells phones also and said he'd give me $100.00 credit to a new factory refirbed, rooted and unlocked dell streak mini if I gave him the one we tried to repair.
I was running CM10 experimental (supposedly stable) build and was having way too many issues: reboots 5+ times a day, random freezes requiring hard reboot, etc etc. I tried uninstalling latest apps...nope. Tried fixing permissions...nope. Finally decided to reinstall the ROM. Used CWM wiped all 3 times, went to istall from zip, couldn't find the ROM anywhere. I installed an older ICS ROM I found in there and it did it's thing until it was time to boot up...now it's stuck in boot loop. I tried removing battery, turning off with both buttons, connecting to usb...not recognized. It just keeps going thru the booting process until it says "Have a nice day!" and then starts over. How do I get in to fix this? I'm screwed....and of course use my phone all day for business......sheesh. Are there ANY JB ROMs out there that are actually stable...like in real life?
Love this site, love all of you helpful folks....pulling my hair out at this point...;-(
You're kinda asking a lot since jb has to be ported over at the moment which naturally leads to glitches such as the restarts. This is the price you pay to run jb months and months before the note is officially updated. at which time the source code will be come available and we will have rock solid jellybean builds. Until then we take what we get. Run the latest release candidate of cm9 until then if you want something super stable.
Also don't you have a backup you can restore? I'm not allowed to feel sorry for you if you never backed up your device.
Sent from my SAMSUNG-SGH-I717 using xda premium
Thanks for the reply JR, your statement " jb has to be ported over at the moment which naturally leads to glitches such as the restarts" is Greek to me. Are you saying that since it is not an official JB update, there will always be glitches? um...ok.
Yes, I have a few backups in there...but as I said, it is stuck in opening boot loop and I don't know how to get in there to restore or flash another ROM. I may be missing a simple fix here but until I know what it is, I don't know what it is. I have used search under boot loop, for an hour and have not found one thread explaining how to get out of it.
Hopefully someone will excuse my ignorance and point me to a thread or explanation of how to get past the boot loop.
Cheers
do you know how to boot into recovery?
if you can, then do that, and restore one of your backups..
if you dont know how to boot into recovery, you shouldn't be flashing roms until you do
AFAIK that means pressing volume up, home, and power until recovery lights up. Done that many times and all I get is the intermittent vibe, no flash, no screen at all.
I've poured over threads and google all day...no love. Just people telling me to restore my backups...gee thanks.
I CAN get it into Odin....can I flash a ROM from there? I followed one tutorial but when selecting a ROM, it wanted a tar file and I either had the ROM zip or unzipped, a bunch of folders with no tar file in any of them.
I'm not a moron, just screwed myself somehow and am looking for some help fixing it. I thought that's what these forums were for.
hold volume up and down and power at the same time; after the first "samsung" on the screen, release the power button, and keep holding the volume up and down, until recovery appears...
XDA is a development forum, not a newbie forum, and there is an assumption that people who flash stuff to their phones will have the basic knowledge to know how to recover from some of the problems that arise when you do something to your phone that requires the knowledge on how to fix things
The fact that you dont know how to get into recovery properly tells me you didnt bother to read and study enough on how to recover from a problem if you have one, sort of like trying to replace your water pump without actually practicing on a car..
search the forums if you need to find .tar files to restore your phone via Odin back to stock; there are several posts and threads that will show you how, but, try to recover your back up first
This ^^^^^. You have jumped into the deep end without knowing how to swim. Watch videos, read how-to's and look up words if you don't understand them. A basic knowledge of computer hardware and how a computer works pre-boot will also go a long way
redman9 said:
Thanks for the reply JR, your statement " jb has to be ported over at the moment which naturally leads to glitches such as the restarts" is Greek to me. Are you saying that since it is not an official JB update, there will always be glitches? um...ok.
Click to expand...
Click to collapse
It means there is no official jelly bean for the note at this time. Our devs have to take jelly bean code and modify it to work on the note which generally means a few hickups here and there.
Sent from my SAMSUNG-SGH-I717 using xda premium
Well thank you all for the help you have given. I was not releasing the power button after the first Samsung flash and thus not finding recovery. I have a functioning phone now, at least. I do, dig deep trying to find answers, and only post when I am truly stuck.
glad you got it fixed!
hboot is 1.15 i am running 1.22.651.3 i have s-on and am unlocked... i am trying to get s off i am trying to flash to cm10 but i cannot get any were can someone please point me in the right direction ... i have read and read and read and nothing adds up to what happens.. .i use clock work mod to download and install when it boots into recovery it says it installs but the screen stays black i have to hard reset (power vol down and camera) it to get anywere then it goes back into recovery and i use the back up file i had to get my phone to work... what am i doing wrong...
No offense to the developer but I would steer clear on CM10 on the Evo. It ran fine on my Nexus but it really didn't do well on my Evo. The MMS didn't work worth a darn. The biggest issue I had was no data. I reflashed it. I wiped everything. I read the instruction 20 times. It just doesn't work well and has some bugs. There seems to always be some major bugs in the AOSP line of roms. Even on the Nexus G AOKP was a constant headache. I wish I could just say do these three steps and all will be flawless. Sorry, that just isn't the case.
Sorry to point this out but this topic goes on the q&a section not on development
HTC EVO LTE
Not sure what kc is talking about I have flawless data and mms on cm10. I have 4g and it works totally fine with no data issues whatsoever. Now the op is posting in the wrong place, but I would gladly help if the post was more clear. So are you s-off or not? If not it will require you to either get s-off or flash the boot.img separately. If you are s-off try using twrp not clockwork. I have been on twrp since I got the Evo in July and have had zero flashing issues.
Sent from my EVO using xda premium
---------- Post added at 09:52 PM ---------- Previous post was at 09:48 PM ----------
I will add mms has been flawless since using Gosms as has been discussed in the cm10 thread multiple times. Not sure if mms works otherwise, but go sms solves it if it is still being worked on. If you don't like/want to us Gosms then just install it solely for mms because it does send and receive them and they show up in the stock messaging app as well.
Sent from my EVO using xda premium
i have s on and all i can access is twrp and hboot
I'm not entirely sure how you managed to put [Q] in your thread title AND ignore the box that says "Is this a question?". There is a very, very clearly labeled section for questions and answers, and your question is one of the most asked here.
Here's your two step fix:
1. Learn where to post. (please)
2. You are S-ON. The reason why you see a black screen is because S-ON users can't flash kernels from recovery. You have to do it seperately. Custom ROMs like AOSP or ROMs that use custom kernels can't be flashed normally on S-ON.
3. No, you did not read. At all. We can tell because the very first thread in the Questions and Answers forum (http://forum.xda-developers.com/showthread.php?t=1869377) says the following:
Note: To those of you with CWM Recovery, it is recommended that you use TeamWin Recovery as it is better suited for our phones.
Brick This is a very serious problem, your device is catatonic and will not respond to the usual methods of power on/off or sim-pull. In some cases the phone comes back when the battery dies and is recharged, this isn't very often. There are un-bricking tools written by OEMs when they screw up (Samsung / Motorola) and there are tools written by developers working on S-OFF. They notice a very real danger and will supply the tool just in case (this is not possible in all cases). Bricking can and will be permanent in many situations
Boot loop There a different kinds of boot loop situations (also referred to as soft brick, please do not cry brick in the forums if it is a boot loop) the most common are a mismatch of kernel and ROM.
Help, my phone is stuck in a boot loop or my phone is stuck on HTC! Not a problem at all. Hold down the power button and continue to hold it, the capacitive buttons will begin flashing and phone will reboot. After the screen turns off let go of power for one second and the press and hold power and volume down to boot into the boot loader. This is known as a simulated battery pull. HTC built this in as a fail safe to reboot your phone, and it gives us a chance to jump into the boot loader should anything go wrong. Once you have successfully made it to the boot loader read through these forms of boot loop to understand what went wrong.
Known forms of boot loop
Generic Boot loop You have a working recovery and now you have installed your first ROM. There's just one problem every ROM you try boot loops but if you restore your back up and it runs fine. This is common when you haven't taken the time to wipe your phone before you flash. You can use a wipe script to clean your phone or you can systematically wipe Dalvik, Cache, Factory Restore, and then wipe System. Now you can flash your custom ROM (HBOOT 1.15+ requires you to flash the kernel separately)
Help my phone won't boot past the splash screen similar to a generic boot loop, the most common fix is to wipe the phone before flashing your ROM. Wipe your dalvik and cache, the factory reset and wipe system. You can now flash your new ROM
Kernel Issue You have flashed a kernel that may be corrupt, originate from a different base, or is just not supported by the ROM (not really the case these days, most developers are willing to share tweaks and custom code) The result is a phone that boots to a black screen and will hang or reboot.
Note: HBOOT 1.15+ requires you to flash the kernel separately, all relevant info to do so is in this guide.
Click to expand...
Click to collapse
In the future, if you have a question, consider placing it the forum that is meant for that. Sorry to sound like an ass, but I'm in a bad mood.
thank for the help...
I am running Cyanogen Mod 10.0 on the phone for 2 weeks and not even one issue. I updated to the latest TWP before I installed the ROM. I am never going back to gay Sense. Sorry but I can't stand sense. I love the build quality of the EVO more than any other phone on the market. I really hope they come out with a Nexus Device.
Download CyanogenMod from their site and you will not have an issue.
Go to the aokp thread and at the beginning says how to push the boot.img vías fast boot after that you should be fine flashing the rom
Sent from my EVO using xda premium
Can someone delete this thread? or move it? or help this guy read instructions on how and where to post things?
Yes I'm closing this. And OP WATCH your language. YOU posted in the wrong area, not the other way around... So it's YOUR fault and No ONE herer owes you ANYTHING.
On a side note, if everyone quotes the offensive language I have to delete that too... just an FYI