Related
for some reason, the 2 times ive flashed custom roms on my phone modaco 1.1 and 1.2 the internet stops working. everything else works perfectly find and the evdo sign shows up, but the internet just does not work. any work around?
and why is it that everytime i try and restore from recovery on my phone, it says
error : run 'nandroid-mobile.sh
restore' via adb!
im guessing i have to run it via my computer and if i do what do i type in??
Joecrack305 said:
for some reason, the 2 times ive flashed custom roms on my phone modaco 1.1 and 1.2 the internet stops working. everything else works perfectly find and the evdo sign shows up, but the internet just does not work. any work around?
Click to expand...
Click to collapse
Several people have reported this, have you tried Fresh rom? Not saying anything against MoDaCo at all, but it seems people have intermitent data issues.
Joecrack305 said:
and why is it that everytime i try and restore from recovery on my phone, it says
error : run 'nandroid-mobile.sh
restore' via adb!
im guessing i have to run it via my computer and if i do what do i type in??
Click to expand...
Click to collapse
This thread may help but I haven't read through it all. Don't know if the answer is there or not.
http://forum.xda-developers.com/showthread.php?t=532719
thanks ill try that and for some reason restore never ever works on my damn phone and the backups are on my phone pretty weird but thanks again
I am running the new Fresh 1.0, he released it last night or this morning. It is GLORIOUS! I LOVE IT. Except, I think the lock screen is a little ugly, I can deal with it though. There are ways to change the lock screen which I may do later today.
i want to use clear as a bell but that doest work yet on 1.0 correct?
post back a link to it and I will load it up and see if it works. Saves you the effort, and i was planning on trying other stuff anyways. Who knows I may like it.
http://forum.xda-developers.com/showthread.php?t=594274
ok just downloaded fresh 0.7 everything works again except internet calls sms everything but no internet???
Just looking back through previous threads of yours. You have run RUU and everything havn't you?
I am at a loss if you have done the RUU and still get no data.
idk what the hell is the problem i ran the ruu back to stock internet is fine i rooted internet still fine flash recovery internet fine install rom internet dead lol
Yeah, thats really odd. Do you have any Root apps installed? Other than maybe WiFi Tether. DroidWall? App manager? anything that could be killing or blocking 3G?
i had droid wall just uninstalled and rebooted i also have overclock widget does that effect it? shouldnt right?
Droid Wall definetly woudl break internet. Maybe it left some stuff behind on the uninstall? A setting or something? Apps2SD is on, it may still have stuff on the SD card. You could try to format it again since you cant actually see that partition...long shot though.
Does the Over Clock widget work? See a difference?
it was droid wall you my friend are the ****! (in a good way of course) lol
might sound stupid but yea overclock does feel like it really work lol. going thru the menu seems so much faster! and when your not using the phone you dial it all the way down, and it really saves the batter
Android 200456, Karl +1 SCORE!
Glad you got it fixed.
people at work are going to hate me lol, i had a customer come in and he was like =O ill pay you lol.i might have to do a side business lol
tethering doesnt work for me on 0.7 =/ it says start tethering stays there then it says su request but it doesnt let me hit always allow because the options dont even show up =/
You should have a Super USer Permisions app in the app drawer. See if the permisions for the app are in there. If they are, long press and delete them. If not, you may have to get the APK for the latest build and push it. Make sure that you Allow all, its the only way mine works at least, otherwise i dont get access.
sorry the reply took so long I didnt get an email that you posted back.
I'm in a bit of a panic and think I need help.
I bought the HTC Hero from Bestbuy roughly Nov. 2009. And like everyone else love it, but was frustrated with all the bugs and slowness, lag ext. Reading and waiting for 2.1, getting impatient weekly...blah blah blah....but horrified to try to root the phone, because im not the techiest guy in the world, so when I saw that there was a 2.1 leak that I could just click from my computer, I did it like an impatient child.
RUU_Hero_C_Sprint_2206511_signed_test.exe
and have had a major problem ever since. The phone will shut off if its not plugged in. I have to constantly turn it back on and wait for it to reboot.
So I followed "How-To repair your bootloader after using the 2.1 RUU" to the T! With no error messages and got it back to "stock" which still looked like 2.1 to me. I formated the SD card from the phone, did a full wipe in that black/green boot page and flashed Beezy's "option 4",
I believe I did a nanbackup right before the "option 4". But I don't think it matters, since the phone was shutting down before that anyway.
So that's where I am. If I'm messing around with the phone (on a call, web, playing with apps) it will stay on, but as soon as I set it down and the screen goes to sleep, thats it, when I pick it up and hit the menu or power button, it reboots (white screen, HTC logo). Am I F'ed? I do have insurance through sprint, but believe that is void now, since I stated messing around with it.
I swapped Batteries with my wife's phone and it still happend, so it's not a bad battery.
I'm sorry if I posted in the wrong forum. I did a search for "constant rebooting" and couldn't find anything similar to my problem.
Thanks in advance.
If all you see is the white htc screen you probably aren't actually rebooting just rosie is restarting. Probably because the ruu doesn't work too well on its own. I suggest you just take the plunge and root, wipe, and flash fresh 2.0d or damage 2.07.2 ( your choice really, both are excellent roms)
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Well, first off it doesn't sound like you are rebooting, it sounds like sense might just be restarting.
Also, don't panic. Whatever you have done is fixable
surely someone who is not posting from their phone will be along to help soon, if not I'll be back home and on my pc in a few hours
Just to confirm
Can you go into settings > about phone > software information (1.5 maybe slightly different I can't remember any more) and tell us what Firmware version says? this way we can make sure that you are running the appropriate version to RUU back to 1.5 and reroot.
I am not sure exactly what is still on your phone.
Also have you ever flashed a radio update from flipz?
I agree, that it isn't rebooting, but its the sense crashing and restarting. I would also agree, that your best option would be to root.
Honestly, the guides are laid out as plain as they could be. It isn't that difficult, you just have to check and re-check typed commands, if done manually.
I think you will be pleasantly surprised and find it simpler than you think.
However, ALWAYS make sure to do to the following:
1. nandroid before you do anything.
2. NEVER EVER NEVER EVER touch anything that doesn't say CDMA HERO. (gsm hero radio flashes can literally fry your nice phone into a nice paperweight)
3. Don't be afraid to ask questions here. I'm pretty new to this, but there are a lot of cool helpful people.
4. nandroid again. (copy nandroids to your PC/Mac and keep a whole library of them.) I even have some extra google space that I've been uploading them to incase I'm not at my computer and I need one...lol)
5. Don't get too sucked into it.
Thank you guys for responding, as I was worried I would get flamed for being an idiot for doing what I did.
"I suggest you just take the plunge and root, wipe, and flash fresh 2.0d or damage 2.07.2 ( your choice really, both are excellent roms) "
Isn't "How-To repair your bootloader after using the 2.1 RUU" basically rooting the phone? Because after I follow those instructions, I get the the recovery menu. I just haven't tried Damage roms yes.
Also, "Well, first off it doesn't sound like you are rebooting, it sounds like sense might just be restarting."
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
I should mention that I have been testing things like, Turning off "Screen Timeout" completely, 10 mins, 1 min, 30 seconds...ext. And it still shuts down after a few minutes when the screen is off......HOWEVER, it is random as far as how long it has been sitting.....Sometimes the screen will be black for a minute and when I hit the menu or power it will reboot....sometimes it will sit for 10 mins and will turn on.....very random, but it WILL reboot eventually.
Thanks again, guys
Chaid said:
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
Click to expand...
Click to collapse
Do you see the first black HTC screen? I know I've done the HTC quietly brilliant screen, but then it goes right to lock screen and loading apps.
I still don't think it is a full reboot, but I'm not THAT up to speed with most of this stuff.
Also, RUU'ing back to stock, then rooting and installing a 2.1 rom by Damagless or Flips should be your best bet.
RUUing back to stock has some problems in and of itself, but it should go ok.
Chaid said:
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
Click to expand...
Click to collapse
Weird...
Regardless, this is fixable.
As Kcarpenter asked, post your system info if you can get to it.
What is your:
Firmware
Baseband
Kernel
Build
Software Number
PRI
PRL
Firmware: 2.1 -update1
Baseband: 2.42.00.03.10
Kernel: 2.6.29-d30020a8
[email protected] #1
Build: 2.20.651.1 CL157175 test-keys
Software Number: 2.20.651.1
PRI: 2.10_003
PRL: 60664
Chaid said:
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
Thanks again, guys
Click to expand...
Click to collapse
Sounds like you are using a 2.1 rom not the stock 1.5
I would try using this guide http://forum.xda-developers.com/showthread.php?t=608434 to correct your issues it will take you back to stock 1.56.651.2 that come with the phone
Oh and if you get any errors this will help too http://forum.xda-developers.com/showthread.php?t=654119
Guys, since he used the 2.1 RUU, isn't he only able to use the 2.1 RUU now? Not the 1.5?
I too am experiencing this.
Factory reset my phone and then flashed from 1.6 to 2.1. I have tried two different 2.1 roms (the sprint leak one and Freshrom) and both of them are causing spontaneous reboots of my phone. I never experienced reboots when on 1.6.
Software information:
2.1 fresh
baseband 1.04.01.09.21
Kernel is 2.6.29-d30020a8
build is fresh rom 2.0d
Software number is 2.20.651.1
PRI is flipz_01
PRL is 60660
any suggestions from anyone?
mrinehart93 said:
Guys, since he used the 2.1 RUU, isn't he only able to use the 2.1 RUU now? Not the 1.5?
Click to expand...
Click to collapse
I believe you are correct, although I have yet to use any RUU
OP, you really should just root the thing flash a rom and succumb to the new obsession you don't even know you have yet
Personally, I'm a fan of RegawMODv2.1, it's lean and stable.
I think that even though you have run 2.1 RUU we can take you back to a bone stock 2.1
When I get home tonight I will try to link to all of the appropriate guides to get you there.
Once we have you back at a stock 1.5 I think we can all say "ROOT IT!" but I would feel more comfortable knowing that you came from the begining in the right order of things.
And get you on a solid stable Rom. I have recently started having issues with my damage rom and all of the aps2sd stuff that has been going on. Not sure what I am going to move to next. But that's besides the point, and none of it is Damageless's fault.
Ok, Kcarpenter, I'll be waiting LOL. I have been f'ing with this thing for a few days now, reading different forums and searching and searching. I finally broke down and posted here, because I'm at a loss. So I REALLY appreciate you guys taking the time to help me. Plugging the phone into my work truck laptop and running to the house to plug it in is wearing me down...
You just need to get over the fear of f*ing up your phone and root it. I'm not sure where the treads are on everything you need, but it's pretty straight forward.
If you had rooted while still running 1.5 you probably would not be in this mess. And Flipz has Fresh Kitchen which makes it even easier to Root and put a recovery console on.
"If you had rooted while still running 1.5 you probably would not be in this mess." You are absolutely correct, &RoidRage. I got excited when I saw the word "Official" 2.1, and jumped the gun.
Chaid said:
"If you had rooted while still running 1.5 you probably would not be in this mess." You are absolutely correct, &RoidRage. I got excited when I saw the word "Official" 2.1, and jumped the gun.
Click to expand...
Click to collapse
That probably created lots of people to get excited.. Anyway, here is what I got
Okay first I looked here
http://forum.xda-developers.com/showthread.php?t=661057&page=6
Which directed me to
http://forum.xda-developers.com/showthread.php?p=6013606#post6013606<--------This is the one you really want.
If you get it to work then you can flash a custom rom. But make sure you download it and put it on the sdcard before doing anything else.
I know it says it is for the 110 error, but people have used it to get back to 1.5 from 2.1
Thanks, man. I'll give it a shot......I have nothing to loose at this point, so I'm over my fear of F'ing up the phone.
I would read everything first, I didn't have the time look it all over.
Editamn predictive text said wetting instead of everything.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
patkin said:
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
Click to expand...
Click to collapse
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
I am not positive what A2SD is. I have a new 8MB SD card that came today. If I pop that in what will happen. Should it be partitioned? Thanks.
Chaid said:
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
Click to expand...
Click to collapse
Thank God I thought I was the only one. I searched but didn't see your thread. Weird problem.
Same problem here too since the new leaked 2.1 test ruu from damaged. The only 2.1 Rom that works for my needs without rebooting every 3rd or 4th time I wake it using the end call/power button is Damagedtrev 2.01, the updated 2.05 Rom in his thread just makes my phone reboot as described above. I don't have a link to his thread, but it would be interesting to see if it worked on your phone too. Other's have claimed a battery shorting might be causing this issue, but I'm not buying that. I've looked at /proc/lastkmsg for clues, but nothing obvious there. I hope the official Sprint update doesn't have this bug or sprint will be giving me a new phone. /end rant
I can't seem to find Damagedtrev 2.01
So I can't test it.
Here's the link to the thread.
I cannot post links, because of some restrictions,but here is the last part of the url.
forum.xda-developers.com/showthread.php?t=653622
here's the link for the full rom
Oops cannot post link to rom on 4shared, look in the bottom of the first post in the thread for a link to the full rom of DamagedTrev_v201
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Ok, downloading......stay tuned.
I really hope this 2.1 ROM works.....I'm kinda sick of 1.5.
Edit:
P.S. I'm reading that there is a battery issue....do you have that?
kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
Hey good news. I put the new SD card in after backing up the other one, partitioned it and copied the files and folders back on then flashed ALOYSIUS and so far so good. I have woken it up about 10 times in a row. Looking good.
I had tried that perticular Rom before with no success.
Interesting.....I'm using the 2 gig sd card that came with the phone....I wonder if that is my problem?
Well it started again. This was right after setting my Gmail and POP3 mail accounts. It shut off on the first sleep after this. Hmmmmm.
I'm re-flashing now and not setting up the mail accounts. Will report back later.
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
reboot
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
It's a full reboot. The phone actually turns off when it goes into sleep. You don't know it's off until you hit the button to wake it up and the phone boots up.
Now for the good news. After re-flashing and not setting up the email accounts it was still shutting downconfused so I started looking elsewhere so I opened up what I thought was a likely culprit in Autokiller and none of the presets where selected so I picked Moderate and haven't had a shutdown since which has been over an hour. Fingers are crossed. I'll report back later.
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
patkin, dude, I felt the same...I gave up on 2.1.
download, wipe then flash Gumbo-1.5c-BARE-signed.zip after it reboots, download and flash Gumbo-Sense-signed.zip.
You flash Gumbo-Sense-signed.zip over the Gumbo-1.5. No need to wipe or anything, it just adds to the ROM. Fast as hell and works PERFECT.
http://www.4shared.com/file/217809392/5fcf1f5d/Gumbo-15c-BARE-signed.html
http://www.4shared.com/file/217811195/3afb5fcf/Gumbo-Sense-signed.html
Give it a shot....I think you will like it......let me know =)
Gumbo thred so you can read up if you like. http://forum.xda-developers.com/showthread.php?t=630221
Chaid said:
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
Click to expand...
Click to collapse
Glad to see your rebooting issue was fixed with this rom even though you went back to gumbo 1.5. In my mind, this just confirms that it is not a battery issue. I never use bluetooth and have never experienced any audio loss with this rom, but apparently even people on the same hardware and firmware versions have different problems.
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
Full Reboot here too.
patkin said:
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
Click to expand...
Click to collapse
Yeah, got my phone beginning of march 2010 and I also think there is something in the 2.1 test ruu or hardware that is keeping the phone from functioning properly with an altered 2.1 rom.
Just wanted to let people know what happened to resolve this. I went back to 1.5 then when 2.1 official came out last week I said what the heck if I can't enjoy a rooted custom 2.1 I'll try the official and guess what. Same problem as the other 2.1's.........phone shuts off randomly! Except this time they are replacing it with a new phone. Yeaaah! I'm probably going Evo now though since I found out I can get a new phone. Anyone need a new Hero?
I'm having the same problem.. One question. Does DarchDroid automatically move dalvik-cache to the sd
Let me preface by saying I'm not a newb, just a newb to the Galaxy S line.
I've rooted other Samsung android phones, no problem.
The day after buying my Epic, I tried to root to use wifi tether and remove bloatware. Not interested in modding right now, as well.... this thing is blazing fast as is. Only complaint so far is of course battery life.
So, following this thread, It bricked my phone.
It successfully rooted, and I even had ADB access to SU, and my android terminal program could get SU.
I then restarted the phone after the "one click" root, and it hangs after the splash screen.
I could still get to the Recovery that was flashed, and tried a wipe of all data/cache etc. No go. The bottom 4 lights stay on, as well as the red LED. Nothing happens. I couldn't get ADB to connect. I never even had the chance to do a Nand backup. The FIRST reboot after booting, "bricked" it. The sprint 4G logo came on, then the Galaxy S splash screen, then hangs.
Took it back to BestBuy (purchased the black tie warranty as well) and the first question he asked is "Did you try and root it." I've bought 3 phones from this guy, and a crap ton of accessories for friends and family, so I was honest and said yeah, I tried. He said no worries, and gave me a new one, but I wasn't the only one to bring in a bricked phone like mine after trying to root.
SO what gives?
After purchasing the phone, there was 2 system updates. The first one downloaded and installed, and about an hour or two after that another one. Is this a patch?
The z4 root option from the market still works (the temporary option, not permanent) and with temp root I can still get WiFi tether to work, so it's not that big of a deal.
However I'm noticing some quirky things that I think a custom ROM may fix.
One: the GPS will randomly activate with no active programs on, not get a fix because I'm inside, and DRAIN the battery. I went from 80% to 17% in about an hour.
Two: The battery percentage/capacity/stats seem to be VERY unstable. I've had the phone at 60%, rebooted, then it shows like 15%. Reboot again and its back up to 50%. Very odd.
Other than that, MY GOD THIS PHONE REALLY IS EPIC. I mean, un freakin' believable. Everything I've EVER wanted from a phone.
http://forum.xda-developers.com/showthread.php?t=771590
Well you didn't actually brick it if the sprint and galaxy s things came on. Could've used odin to reset it to factory.
poor_red_neck said:
Let me preface by saying I'm not a newb, just a newb to the Galaxy S line.
I've rooted other Samsung android phones, no problem.
The day after buying my Epic, I tried to root to use wifi tether and remove bloatware. Not interested in modding right now, as well.... this thing is blazing fast as is. Only complaint so far is of course battery life.
So, following this thread, It bricked my phone.
It successfully rooted, and I even had ADB access to SU, and my android terminal program could get SU.
I then restarted the phone after the "one click" root, and it hangs after the splash screen.
I could still get to the Recovery that was flashed, and tried a wipe of all data/cache etc. No go. The bottom 4 lights stay on, as well as the red LED. Nothing happens. I couldn't get ADB to connect. I never even had the chance to do a Nand backup. The FIRST reboot after booting, "bricked" it. The sprint 4G logo came on, then the Galaxy S splash screen, then hangs.
Took it back to BestBuy (purchased the black tie warranty as well) and the first question he asked is "Did you try and root it." I've bought 3 phones from this guy, and a crap ton of accessories for friends and family, so I was honest and said yeah, I tried. He said no worries, and gave me a new one, but I wasn't the only one to bring in a bricked phone like mine after trying to root.
SO what gives?
After purchasing the phone, there was 2 system updates. The first one downloaded and installed, and about an hour or two after that another one. Is this a patch?
The z4 root option from the market still works (the temporary option, not permanent) and with temp root I can still get WiFi tether to work, so it's not that big of a deal.
However I'm noticing some quirky things that I think a custom ROM may fix.
One: the GPS will randomly activate with no active programs on, not get a fix because I'm inside, and DRAIN the battery. I went from 80% to 17% in about an hour.
Two: The battery percentage/capacity/stats seem to be VERY unstable. I've had the phone at 60%, rebooted, then it shows like 15%. Reboot again and its back up to 50%. Very odd.
Other than that, MY GOD THIS PHONE REALLY IS EPIC. I mean, un freakin' believable. Everything I've EVER wanted from a phone.
Click to expand...
Click to collapse
black screen of death. reflash stock .tar with odin. happened less than an hour after i bought mine.
LucJoe said:
http://forum.xda-developers.com/showthread.php?t=771590
Click to expand...
Click to collapse
Wow, that was helpful. Thanks.
If the vbulleting search feature didn't blow donkey balls so hard, then maybe I could find an answer. Instead all I find are generic results that happen to have the word root or brick in them, none of which applied to my scenario.
If this belongs in General, then my apologies. In the hero forum we didn't discuss rooting, or ROMs in General section. It was all in Development.
So should I just try again, or is there something I'm doing wrong? I mean how hard is it to screw up a one click root???
I'd actually be more comfortable doing it through ADB...
Try again. Make sure you use a good usb cable and you connect through the back of your computer. Restart phone and computer to be safe.
If you "brick" it again just use Odin to flash the stock tar.. you were never truly bricked!
poor_red_neck said:
Let me preface by saying I'm not a newb, just a newb to the Galaxy S line.
I've rooted other Samsung android phones, no problem.
The day after buying my Epic, I tried to root to use wifi tether and remove bloatware. Not interested in modding right now, as well.... this thing is blazing fast as is. Only complaint so far is of course battery life.
So, following this thread, It bricked my phone.
It successfully rooted, and I even had ADB access to SU, and my android terminal program could get SU.
I then restarted the phone after the "one click" root, and it hangs after the splash screen.
I could still get to the Recovery that was flashed, and tried a wipe of all data/cache etc. No go. The bottom 4 lights stay on, as well as the red LED. Nothing happens. I couldn't get ADB to connect. I never even had the chance to do a Nand backup. The FIRST reboot after booting, "bricked" it. The sprint 4G logo came on, then the Galaxy S splash screen, then hangs.
Took it back to BestBuy (purchased the black tie warranty as well) and the first question he asked is "Did you try and root it." I've bought 3 phones from this guy, and a crap ton of accessories for friends and family, so I was honest and said yeah, I tried. He said no worries, and gave me a new one, but I wasn't the only one to bring in a bricked phone like mine after trying to root.
SO what gives?
After purchasing the phone, there was 2 system updates. The first one downloaded and installed, and about an hour or two after that another one. Is this a patch?
The z4 root option from the market still works (the temporary option, not permanent) and with temp root I can still get WiFi tether to work, so it's not that big of a deal.
However I'm noticing some quirky things that I think a custom ROM may fix.
One: the GPS will randomly activate with no active programs on, not get a fix because I'm inside, and DRAIN the battery. I went from 80% to 17% in about an hour.
Two: The battery percentage/capacity/stats seem to be VERY unstable. I've had the phone at 60%, rebooted, then it shows like 15%. Reboot again and its back up to 50%. Very odd.
Other than that, MY GOD THIS PHONE REALLY IS EPIC. I mean, un freakin' believable. Everything I've EVER wanted from a phone.
Click to expand...
Click to collapse
Lol. Agree. I screamed and yelled at htc ppcs cuz they lack 3d gpu power.and cripple features on their hsndsets. Now im a samsung costumer for life. Even faster than iphone 4. Love it!
Sent from my SPH-D700 using Tapatalk
Try the drockstar all in one root v2.01, worked like a charm for me rerooting the other day. Had some issues with the one click the first time awhile ago.
You didn't really brick your phone. Hold 1 when you power up to enter download mode. Make sure you firewall and antivirus are disabled, odin wouldn't work with my Norton AV. Then you can always flash the stock D18 through Odin.
You should root asap. Like they said you can allways flash to stock if something happens instead of returning the phone. I remember I used to use my phone all day connected to a power supply. Now I don't have to do it with the syndicate rom and my phone is even faster.
Sent from my SPH-D700 using XDA App
You didnt brick your phone. I have had that screen hang for 6-7 minutes many of times after rooting or flashing. Because that is when your kernel and files get rebuilt at that splash screen so it is really slow and feels like forever but it will boot. If not battery pull and try to boot again or use odin.
poor_red_neck said:
Let me preface by saying I'm not a newb, just a newb to the Galaxy S line.
I've rooted other Samsung android phones, no problem.
The day after buying my Epic, I tried to root to use wifi tether and remove bloatware. Not interested in modding right now, as well.... this thing is blazing fast as is. Only complaint so far is of course battery life.
So, following this thread, It bricked my phone.
It successfully rooted, and I even had ADB access to SU, and my android terminal program could get SU.
I then restarted the phone after the "one click" root, and it hangs after the splash screen.
I could still get to the Recovery that was flashed, and tried a wipe of all data/cache etc. No go. The bottom 4 lights stay on, as well as the red LED. Nothing happens. I couldn't get ADB to connect. I never even had the chance to do a Nand backup. The FIRST reboot after booting, "bricked" it. The sprint 4G logo came on, then the Galaxy S splash screen, then hangs.
Took it back to BestBuy (purchased the black tie warranty as well) and the first question he asked is "Did you try and root it." I've bought 3 phones from this guy, and a crap ton of accessories for friends and family, so I was honest and said yeah, I tried. He said no worries, and gave me a new one, but I wasn't the only one to bring in a bricked phone like mine after trying to root.
SO what gives?
After purchasing the phone, there was 2 system updates. The first one downloaded and installed, and about an hour or two after that another one. Is this a patch?
The z4 root option from the market still works (the temporary option, not permanent) and with temp root I can still get WiFi tether to work, so it's not that big of a deal.
However I'm noticing some quirky things that I think a custom ROM may fix.
One: the GPS will randomly activate with no active programs on, not get a fix because I'm inside, and DRAIN the battery. I went from 80% to 17% in about an hour.
Two: The battery percentage/capacity/stats seem to be VERY unstable. I've had the phone at 60%, rebooted, then it shows like 15%. Reboot again and its back up to 50%. Very odd.
Other than that, MY GOD THIS PHONE REALLY IS EPIC. I mean, un freakin' believable. Everything I've EVER wanted from a phone.
Click to expand...
Click to collapse
Well 1st things 1st. Your phone WAS NOT BRICKED!!! All you had to do was use Odin to flash your phone back to stock! If you would have done your homework, you woulda known that! But you didnt! Cuz your too freakin LAZY to READ!!!! A EPIC CONNOT BE BRICKED UNLESS YOUR A IDIOT!!!!
@OP
Hey man, did you try this procedure?
http://forum.xda-developers.com/showthread.php?t=773032&highlight=revert+stock
Good luck and don't give up on it!
It is fully possible to Brick an Epic... a fair amount of idiocy is involved though.
Epic Experience 1.2.0.9/Phoenix 1.49s/Elegant Steel .21
Damn, I always rush into these topics thinking someone bricked their phone, but turns out most of the time it's just someone else misusing that word
sniperkill said:
Well 1st things 1st. Your phone WAS NOT BRICKED!!! All you had to do was use Odin to flash your phone back to stock! If you would have done your homework, you woulda known that! But you didnt! Cuz your too freakin LAZY to READ!!!! A EPIC CONNOT BE BRICKED UNLESS YOUR A IDIOT!!!!
Click to expand...
Click to collapse
Should I release the angry grand wizard kkk silverback gorilla on him? Lol.
Sent from my SPH-D700 using Tapatalk
If I use the current version of VISIONary (r14) and ONLY temp-root my MT4G, will ANY residual effects be left once I reboot?
I remember when using VISIONary on my MT3G, it seemed to cause permanent changes even though I only used "temp" root.. eventually my phone seemed to have conflicts with apps and it never really "unrooted"
It's my understanding that VISIONary should be completely safe as it does not write to the system partition..?
Please move this to q&a......
From my don't talk about changelog CM7 Glacier
Anyone?? Need some advice here.
$pitacular1 said:
Anyone?? Need some advice here.
Click to expand...
Click to collapse
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
neidlinger said:
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
Click to expand...
Click to collapse
In the modaco forum I read earlier today that someone was having constant reboots from using VISIONary for temp root.
You said your wife's phone "had zero usability problems after a reboot". What about after temp-rooting, but before rebooting? Any issues there?
$pitacular1 said:
In the modaco forum I read earlier today that someone was having constant reboots from using VISIONary for temp root.
You said your wife's phone "had zero usability problems after a reboot". What about after temp-rooting, but before rebooting? Any issues there?
Click to expand...
Click to collapse
Nope she uses it all day everyday.
Thank you, much appreciated.
Temp-Root here I come!
Btw, is she using the latest version (r14) ?
Noticed no problems
I've seen no problems after a reboot with Visionary r14. On another point, I had it originally set to automatically temproot after every reboot, but once I discovered that the programs that Titanium Pro freezes stay frozen after a reboot even if you're not temprooted, I no longer temproot. Have to use it, though, if I want to add/subtract frozen programs.
ecdy said:
I've seen no problems after a reboot with Visionary r14. On another point, I had it originally set to automatically temproot after every reboot, but once I discovered that the programs that Titanium Pro freezes stay frozen after a reboot even if you're not temprooted, I no longer temproot. Have to use it, though, if I want to add/subtract frozen programs.
Click to expand...
Click to collapse
I wonder if that's normal. It was residual root-like effects like that I was wondering about.
neidlinger said:
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
Click to expand...
Click to collapse
On another note, I had previously experimented on my MT3G with Universal Androot which worked perfectly.. it was only later after the 2.2 update that I needed a root alternative as they had patched the exploits Universal Androot used to get root.. VISIONary was a perfect solution. The only problem is it resulted a permanent "partial" root instead of a temporary root or a full perm root. It was still an excellent tool to use for the job though.. nothing went "FUBAR" lol I was still able to SAPPIMG and then manually update to the official Froyo.
I was just curious if I was going to get the same perm root issue with the MT4G, as I have not yet familiarized myself with the process of restoring the 4G to stock although I am aware of PD15IMG.. just haven't read through the specifics. I swear I'm not a total noob I promise.. I've written tutorials on root for the MT3G
Ok, so last night I used VISIONary for temp root only..
Immediately after temp rooting, my phone started acting weird.. syncing extra long, everything was slow (even after the syncing).. it just seemed to be severly affecting the performance of my device.
I don't know if perhaps I have an active app it was having issues working with or what, all I know is without temp root my phone flies 24-7.
Once I rebooted, everything went back to normal. Don't think I'll be using VISIONary anymore
$pitacular1 said:
Ok, so last night I used VISIONary for temp root only..
Immediately after temp rooting, my phone started acting weird.. syncing extra long, everything was slow (even after the syncing).. it just seemed to be severly affecting the performance of my device.
I don't know if perhaps I have an active app it was having issues working with or what, all I know is without temp root my phone flies 24-7.
Once I rebooted, everything went back to normal. Don't think I'll be using VISIONary anymore
Click to expand...
Click to collapse
i guess you are one in a million who have experienced problems with VISIONary.apk.
I guess if you are that bent on rooting you can do it the old fashioned way.
neidlinger said:
i guess you are one in a million who have experienced problems with VISIONary.apk.
I guess if you are that bent on rooting you can do it the old fashioned way.
Click to expand...
Click to collapse
Well last night when I first tried it, I had not enabled USB debugging..
So this morning, I tried it again, but made sure it was enabled the FIRST time lol..
and it's working flawlessly. I guess my initial idiocy caused something.. but it's fine now!
$pitacular1 said:
Well last night when I first tried it, I had not enabled USB debugging..
So this morning, I tried it again, but made sure it was enabled the FIRST time lol..
and it's working flawlessly. I guess my initial idiocy caused something.. but it's fine now!
Click to expand...
Click to collapse
That's cool. Glad to hear it is working.