I unlocked the Boot loader and installed CWM via recovery partition flash. I noticed that after that my a cant resolve an ip with 4g service. I had massive 4G coverage before the unlocking procedure. Im starting a new thread because the last thing i want to do is have to downgrade back to stock. It would be a terrible waste of time to have unlocked and backed myself up.
I also cleard dalvik cache and fixed permissions via CWM.
no luck.
This has been an ongoing issue. So far nobody who unlocked has 4g, its not you. If 4g is that important you can SBF to the official CM5 release from Motorola. While your device will remain physically unlocked, you will lose all the benefits until you flash pudding again. However if you relock the phone you will regain 4g access. Since the devs are working on fixing 4g I don't expect any serious ROMs at the moment, you might as well relock and gain your 4g access back. For me, there is no 4g in my area so I'm not so bothered by this problem. I'm confident they will fix it, they just have to find the right radio files and release a flash able update that you do after unlocking the bootloader.
Please keep these posts under the correct topic or post them in the Q&A section. People are working on this and your feedback is welcome under the correct topic (IE: pudding or the other unlock thread).
if you doubt my sincerity you may be infracted by a mod for posting things like this in the wrong section for sure.
the2dcour said:
Please keep these posts under the correct topic or post them in the Q&A section. People are working on this and your feedback is welcome under the correct topic (IE: pudding or the other unlock thread).
if you doubt my sincerity you may be infracted by a mod for posting things like this in the wrong section for sure.
Click to expand...
Click to collapse
Sorry but I don't agree that this is in the wrong section. You or one of the others should have made a new post regarding this, or updated the other posts accordingly, the fact that you haven't is beyond me. I would rather look at a shorter thread than have to surf through pages of a thread to find the answer we are all still looking for.
The unlocked bootloader thread should have been updated as soon as you guys knew it was breaking people's 4g. There should have been some kind of edit that stated this fact.
As of this post, the 'unlock your bootloader here' thread still doesn't warn people that it breaks their 4g. I find it very unprofessional that the OP has not put something up regarding this.
Don't get me wrong, I appreciate what you all have done, but giving people all the information is also part of what you guys should be doing. Not making people read 15 pages worth of **** just to find out the unlock they did f'd there **** up.
EDIT: If this thread doesn't qualify then put your own up and title it accordingly, because we should already have a thread up about this as most of us are patiently waiting for a fix.
Flame me if you must, but its the truth.
-DJ
I don't know about you guys but I love my Photon 3g. I can't wait to get CM7 on this.
I also love my Photon now that it's rooted. But, I FULLY agree with OP that proper warning should exist on ALL threads regarding rooting/unlocked bootloader that you will lose 4G once you go that route.
the2dcour said:
Please keep these posts under the correct topic or post them in the Q&A section. People are working on this and your feedback is welcome under the correct topic (IE: pudding or the other unlock thread).
if you doubt my sincerity you may be infracted by a mod for posting things like this in the wrong section for sure.
Click to expand...
Click to collapse
+10 char.
Sent from my MB855 using XDA App
I u locked my phone using the big 400mb sbf. Then i rebooted and used the system.img then i rebooted again and wiped recovery and flashed cwm. When i rebooted i did the initial setup and restored everything from titanium backup. After that i rebooted again and i had 4g all my apps in the market and things have been working perfectly.
Also during the flashing i removed my sim and sd card and put them back before running setup.
Sent from my MB855 using XDA App
Thexfactor2011 said:
I u locked my phone using the big 400mb sbf. Then i rebooted and used the system.img then i rebooted again and wiped recovery and flashed cwm. When i rebooted i did the initial setup and restored everything from titanium backup. After that i rebooted again and i had 4g all my apps in the market and things have been working perfectly.
Also during the flashing i removed my sim and sd card and put them back before running setup.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
By the way, did you unlock the bootloader or just did regular root. People lost the 4g connectivity because they unlocked the bootloader. Please clearify. Thanks
urcboss07 said:
By the way, did you unlock the bootloader or just did regular root. People lost the 4g connectivity because they unlocked the bootloader. Please clearify. Thanks
Click to expand...
Click to collapse
Sorry for the delay. Freaking meetings all morning.
Well to flash the system.img for root you have to have an unlocked bootloader. So to clarify.
1. Charged to 100% removed sim, and sd card, backed up apps, and data.
2. Flashed the 400mb pudding sbf
3. rebooted
4. ran the unlock command
5. rebooted again
6. After it booted turned it of and put back in flashback
7. rooted the phone using system.img and flashback.
8. without rebooting flashed cwm img blue to be exact
9. rebooted
10. completed android setup and installed titanium backup root and superuser
11. restored everything via titanium apps, and data
12. rebooted
13. cleared both caches
14. started the phone up and I have all my apps in the market and 4g
To note though I live in Philly and the night I unlocked and rooted i had 4g(Sunday), I had spotty 4g on Monday it would connect and then disconnect and sometimes just turn off and on and refresh, Today It keeps finding sprint saying connecting and then just restarts and does it again.
The only thing that has happened between the fully working to questionable connectivity was that I let my battery completely die and the phone shut off.
to summarize I believe I have the same problem as everyone else now. No connecting 4g
Sent from my Nexus S 4G using Tapatalk
Djspinister said:
The unlocked bootloader thread should have been updated as soon as you guys knew it was breaking people's 4g. There should have been some kind of edit that stated this fact.
As of this post, the 'unlock your bootloader here' thread still doesn't warn people that it breaks their 4g. I find it very unprofessional that the OP has not put something up regarding this.
Don't get me wrong, I appreciate what you all have done, but giving people all the information is also part of what you guys should be doing. Not making people read 15 pages worth of **** just to find out the unlock they did f'd there **** up.
EDIT: If this thread doesn't qualify then put your own up and title it accordingly, because we should already have a thread up about this as most of us are patiently waiting for a fix.
Flame me if you must, but its the truth.
-DJ
Click to expand...
Click to collapse
Well, the Unlocked Bootloader thread by Yay does have the notice in its title. Whether that was done after this thread pointed it out, I don't know, but regardless. It should have been made in that thread and a pm should have been sent to Yay asking him to make a mention of it either in the title or in his first post. Making other threads is just going to clutter up the forum.
Mods please close.
TS out
Moved to proper forum and locked because it is already stated in the unlock bootloader thread
Related
I have just rooted my Photon. Pretty happy with it. Wasn't as hard as I thought it was gonna be. Now to overclock it am I gonna have to flash a custom ROM? And if I indeed have to flash a custom ROM, do I have to unlock my bootloader? Or is there a way around that? Thanks for all the info.
There's a few threads floating around about unlocking your bootloader; id be careful though you could possibly break 4G. As far as kernels go, the source was released a week ago so you cant overclock until a dev releases a kernel. You'd need to flash a custom kernel in order to flash roms...
I rooted my phone and left it stock just for a few root apps at least until a new bootloader unlocking method is found and a kernel is ready!
Bootloader thread. Fyi there are ways to retain 4G just check development section.
http://forum.xda-developers.com/showthread.php?t=1216097
As soon as android.git.kernel.org comes back up I'm going to pull in some source code and see if I can cook up a CyanogenMod kernel.
Cool appreciate all the info guys. And as for the 4G. I don't use it and it's not in my area. So I'm not very worried about that to be quite honest. I'm having trouble tryin' to flash a custom ROM on my phone as of now. I don't seem to be doing it right.
Okay. As you two seem to know what's going on. I just flashed the Laser ROM onto my phone. And the su binary is outdated. But when I update, the superuser force closes. Is this common with custom ROM's? I tried to ask in the development page, but as I don't have enough posts, it wouldn't let me post there. Thanks! Also, as a side note. I didn't seem to have to unlock my bootloader to do the laser ROM but the Alien one says I do? Is this true? Again, I know this isn't the right area. but it's the only place I can post. Thanks again guys.
xTMFxOffshore said:
Okay. As you two seem to know what's going on. I just flashed the Laser ROM onto my phone. And the su binary is outdated. But when I update, the superuser force closes. Is this common with custom ROM's? I tried to ask in the development page, but as I don't have enough posts, it wouldn't let me post there. Thanks! Also, as a side note. I didn't seem to have to unlock my bootloader to do the laser ROM but the Alien one says I do? Is this true? Again, I know this isn't the right area. but it's the only place I can post. Thanks again guys.
Click to expand...
Click to collapse
Assuming you flashed the latest custom recovery right? Also there's an app in the market that helps with the updating of superuser if it fails. Its called "superuser update fixer"; maybe that will help as i didnt have that issue. Yes with alien rom you do but there's a guide that lets you retain 4G with the alien rom.
Bootloader unlock instructions with alien link.
http://forum.xda-developers.com/showthread.php?t=1227867
Thanks Kenny. I appreciate the info. I got that first issue with the su fixed. And I flashed the Laser P-Rom with cwm or whatever it's called. As for 4G, not too concerned with that. But I will see about unlocking the bootloader today. I appreciate all the info.
xTMFxOffshore said:
Thanks Kenny. I appreciate the info. I got that first issue with the su fixed. And I flashed the Laser P-Rom with cwm or whatever it's called. As for 4G, not too concerned with that. But I will see about unlocking the bootloader today. I appreciate all the info.
Click to expand...
Click to collapse
If you don't need 4G then flash away and unlock bootloader dude you should have no issues
Yeah. I'm gonna run out and do some stuff, come home then unlock my bootloader and flash that Alien ROM. How difficult is it to unlock the bootloader?
xTMFxOffshore said:
Yeah. I'm gonna run out and do some stuff, come home then unlock my bootloader and flash that Alien ROM. How difficult is it to unlock the bootloader?
Click to expand...
Click to collapse
Not difficult at all if you managed to root your phone lol
Overclock photon pleaseee
I want to know who's gonna be the first to post a overclock kernel for the photon
Cool Thanks again Man. I'm gonna try to do this tonight. But I keep getting caught up working on someones car or doing something of that nature. ha. But tonight hopefully! I'll post back once I do it and get the Alien ROM flashed.
No such luck, I can't flash the SDF file or something like that. and I'm not really all that intune with what I'm doing. So I don't know what's wrong and I keep getting a failed when I try to flash it. So I think I'm just kinda stuck not having an unlocked bootloader.
Okay. As I wanted to throw my phone at the wall but though better of it. And I really don't understand the Pudding thread. As I read through it. I used this http://briefmobile.com/motorola-photon-4g-bootloader-unlocked to no avail. I got a fail to flash on RSD Lite when attempting to flash the derpun.spf So now that I've come to a point of impass. Any ideas?
xTMFxOffshore said:
Okay. As I wanted to throw my phone at the wall but though better of it. And I really don't understand the Pudding thread. As I read through it. I used this http://briefmobile.com/motorola-photon-4g-bootloader-unlocked to no avail. I got a fail to flash on RSD Lite when attempting to flash the derpun.spf So now that I've come to a point of impass. Any ideas?
Click to expand...
Click to collapse
Was your phone at least 50% charged when you attempted it? If it wasn't you will get errors! Maybe you skipped out on a command? You should try posting the error you're getting in the bootloader thread so a few devs can see it. I would imagine many of them hang around their section and not general lol.
http://forum.xda-developers.com/showthread.php?t=1216097
It's the same error that photon pudding thread spoke of, Tried to use that fix. Didn't work. And the rest of it I can't make any sense of. I don't follow it, and the stupid site I used didn't work. So unless there is an easier way that is more clear to unlock it. I think I'm SOL.
xTMFxOffshore said:
It's the same error that photon pudding thread spoke of, Tried to use that fix. Didn't work. And the rest of it I can't make any sense of. I don't follow it, and the stupid site I used didn't work. So unless there is an easier way that is more clear to unlock it. I think I'm SOL.
Click to expand...
Click to collapse
Im waiting for an easier method myself that doesn't break 4G. Lol.
Yeah, someone was saying that his flash failed, but to run the fastboot. now I'm stuck at that. How the hell do I run the fastboot? haha.
Got it done. :]
xTMFxOffshore said:
Got it done. :]
Click to expand...
Click to collapse
Nice!!!! Im sure you're ready to flash away lol. Congrats dude!
I'm to HTC and rooting a phone. Wanted to know how hard it is to root and what is a good safe rom to go with for my first try. Thxs, any help would be useful
Since your new, might I suggest the search button? Your exact question has been asked a few times before.
Sent from my ADR6425LVW using XDA App
It's not hard at all. I suggest you read a lot before you do anything though. There are several guides in the dev section and you would do yourself a favor to read all of them as well as the replies in the thread. And read the entire thread of any ROM you are thinking of flashing. List of guides, roms, kernels etc here: http://forum.xda-developers.com/showthread.php?t=1425091
First thing to do is check if you have the update or not. You'll want it before you unlock and root. Go into Settings > About phone > More and see if your baseband is 0.95.00.1118r, 0.95.00.1223r and your software should be 2.x. I don't have the exact number because I went with a ROM that is based on the build before the OTA. If your baseband matches the above you should have the update and are ready to unlock.
Follow the instructions here to unlock:
http://forum.xda-developers.com/showthread.php?p=20780879#post20780879
Once you are unlocked you will want to flash Amon Ra, a custom recovery, which will let you make backups and flash stuff easier and allow you to root.
Get that here:
http://forum.xda-developers.com/showthread.php?t=1339679
Put that img file in the same folder you used for unlocking.
Boot your phone into bootloader by shutting down, pull the battery and put it back, hold volume down + power until the white bootloader screen comes up. Select fastboot, connect it to your pc and use the following command:
fastboot flash recovery nameofrecovery.img
Once that is flashed, select bootloader, then recovery. Navigate to the developer menu in recovery and install su. Now you are rooted. I would make a nandroid in recovery at this point and label it as stock rooted so you always have this to go back to should you have any problems.
Then pick a ROM and the instructions for flashing that will be in the thread. I would stick to GB until you are more comfortable then you can try ICS. ICS ROMs are still a bit buggy and don't have everything functioning perfectly so read up before you flash any of them.
Ineffabilis is a good ROM that I've used. People like CleanRom and Nils Business Sense. You should just read the threads and see what they offer and pick one. You can always try another one afterwards.
nosympathy said:
Since your new, might I suggest the search button? Your exact question has been asked a few times before.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
^ This. I'm all for answering questions and everything, but it's annoying when people don't even try to search for the answer themselves. But there is always someone that will answer their question... So the cycle will go on.
I agree one should do there own research, but rooting can be a little overwhelming to someone that is new to it. Its ok to ask for a little guidance.
stelv said:
I agree one should do there own research, but rooting can be a little overwhelming to someone that is new to it. Its ok to ask for a little guidance.
Click to expand...
Click to collapse
The point to be made is to ask in one of the threads that was already created(and found via search). I can honestly say that it doesn't matter either way to me. A little forum etiquette would be nice though.
I'm very familiar with Samsung and Odin, but Motorola stuff its confusing as hell. I've got a Photon now (and my ET4G). I've been reading through the stickies and the general / Q&A section and can't seen to find a definitive answer to a few questions...
1. I am 2.3.4 running 4.5.1A-1_SUN-198_6. What is the latest root method?
2. Do I need an unlocked bootloader to flash roms and kernels?
3. Any fix for the random "sleep of death" without updating to 2.3.5?
Thanks in advance for any help you all can give!
- Z
zzelinka said:
I'm very familiar with Samsung and Odin, but Motorola stuff its confusing as hell. I've got a Photon now (and my ET4G). I've been reading through the stickies and the general / Q&A section and can't seen to find a definitive answer to a few questions...
1. I am 2.3.4 running 4.5.1A-1_SUN-198_6. What is the latest root method?
2. Do I need an unlocked bootloader to flash roms and kernels?
3. Any fix for the random "sleep of death" without updating to 2.3.5?
Thanks in advance for any help you all can give!
- Z
Click to expand...
Click to collapse
Funny because Samsung's are the complicated ones. All rooting info is listed in development section. One click root should work.
And yes you must of course unlock the bootloader to do any of that.
Sleep of death? Heard of it from like two random people. Never had it happen.
Sent from my SGH-I777 using XDA
zzelinka said:
I'm very familiar with Samsung and Odin, but Motorola stuff its confusing as hell. I've got a Photon now (and my ET4G). I've been reading through the stickies and the general / Q&A section and can't seen to find a definitive answer to a few questions...
1. I am 2.3.4 running 4.5.1A-1_SUN-198_6. What is the latest root method?
2. Do I need an unlocked bootloader to flash roms and kernels?
3. Any fix for the random "sleep of death" without updating to 2.3.5?
Thanks in advance for any help you all can give!
- Z
Click to expand...
Click to collapse
if you are familiar with odin then its gunna be a breeze, tars = sbf's, and odin = rsd lite. if you bork something youve gutta get into the proper mode (download mode = rsd mode) load up rsdlite and add the sbf in and click start.
shabbypenguin said:
if you are familiar with odin then its gunna be a breeze, tars = sbf's, and odin = rsd lite. if you bork something youve gutta get into the proper mode (download mode = rsd mode) load up rsdlite and add the sbf in and click start.
Click to expand...
Click to collapse
Cool. I am contemplating just updating to the newest update and not needing with anything for now. I pretty much bought it to use for my $59.99 lapdock. I actually bought two off Craigslist for $230. They are both pretty much brand new and came with original boxes, etc.
I'm still on the fence. It randomly shuts off and won't turn back on without a battery pull. Its frustrating as hell. Its done it probably 5-10 times tonight alone, and tonights the first night I've had it! I've read that updating to the newest system update takes care of the problem.
- Z
na7q said:
Funny because Samsung's are the complicated ones. All rooting info is listed in development section. One click root should work.
And yes you must of course unlock the bootloader to do any of that.
Sleep of death? Heard of it from like two random people. Never had it happen.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
It just seems like its so much more complicated. Seems like I can brick my phone more easily with all this Moto software.
- Z
zzelinka said:
It just seems like its so much more complicated. Seems like I can brick my phone more easily with all this Moto software.
- Z
Click to expand...
Click to collapse
I urge you not to take the 2.3.5 as if it doesn't fix your sleep of death, there is literally no way to get it off your phone. Our stuff only seems a bit confusing because there is an extra step in there (unlocking) that you people don't have to contend with. Also, we lack a definitive AIO that does everything within one program. It takes a bit of getting used to but as shabby said, the concept is generally the same and there are simple guides for each step.
-Root using torpedo method (aio will probably work but torpedo never fails)
-unlock bootloader
-install a recovery (twrp is fine but you're probably used to cwm)
-flash yo sheet
Acvice said:
I urge you not to take the 2.3.5 as if it doesn't fix your sleep of death, there is literally no way to get it off your phone. Our stuff only seems a bit confusing because there is an extra step in there (unlocking) that you people don't have to contend with. Also, we lack a definitive AIO that does everything within one program. It takes a bit of getting used to but as shabby said, the concept is generally the same and there are simple guides for each step.
-Root using torpedo method (aio will probably work but torpedo never fails)
-unlock bootloader
-install a recovery (twrp is fine but you're probably used to cwm)
-flash yo sheet
Click to expand...
Click to collapse
Werd. Was there ever a fix for sleep of death?
Do not update it with ota.
Flash 198_7 sbf and then flash only locked bootloader from 2.3.4 sv1 custom sbf thread.
It should solve the problem.
peetr_ said:
Do not update it with ota.
Flash 198_7 sbf and then flash only locked bootloader from 2.3.4 sv1 custom sbf thread.
It should solve the problem.
Click to expand...
Click to collapse
I'll check it out. Thanks for the info!
- Z
peetr_ said:
Do not update it with ota.
Flash 198_7 sbf and then flash only locked bootloader from 2.3.4 sv1 custom sbf thread.
It should solve the problem.
Click to expand...
Click to collapse
I saw the SV1 Locked Bootloader.sbf.zip but no 198_7 file. Am I missing something obvious. I probably am
EDITED: I'm a moron. Found it on Loikifish's site...
One more question, your phone is unlocked or locked, when the sleep of death problem occurs?
peetr_ said:
One more question, your phone is unlocked or locked, when the sleep of death problem occurs?
Click to expand...
Click to collapse
It's unlocked. Totally stock, nothing on it. No apps, nada. Just takes a nap on me and never wakes up... I switched back to my ET4G for now. At least until I can get the sleep of death figured out. Any help would be greatly appreciated. Gonna sell one of my MoPho's and maybe the second one w/ my lapdock if I figure out what to do about it. I don't want to pay to get a replacement either....
- Z
Ok so do what I wrote before, that should solve the problem an you will stay unlocked.
Actually you can try, that just flashing 198_7 sbf and not unlocking, will solve the problem.
I mistyped. It's LOCKED. Should I still just flash the 198 and the locked only?
EDIT: Shabby's AIO worked and I'm thinking about unlocking the bootloader. I can't remember if I saw somewhere where I can retain 4G with unlocking the BL. I can't seem to find it now...
Yes, if it's 198_6 now, you can flash 198_7 sbf, so that 2.3.5 update won't bother you and unlock only with bootloader, not derpunlock.sbf.
Tell me, if that helped with those deaths.
So I did an expirement to test a theory... I activated my Photon on my line the day before yesterday. I had a sleep of death if I let the phone sit too long (maybe 20-30 minutes). I was in good radio areas. I took the Photon off my line and let it sit to see if it would go to sleep and not wake up.
Guess what? I left it on for 12+ hours unattended and when I went to turn it on... No sleep of death! I'm going to put it back on my line and see if it sleeps hard again. I think we can then say the problem is most likely some sort of radio related. Am I correct?
- Z
It is possible. You could try to find out where is the problem on yours.
I only know, that one man had this problem everytime he tried to unlock his phone with derpunlock.sbf. When he flashed full 198_7 sbf, everything was fine. Once he tried to unlock different way, that sleep of death was gone.
But this looks like the cause of your problem could be somewhere else.
peetr_ said:
It is possible. You could try to find out where is the problem on yours.
I only know, that one man had this problem everytime he tried to unlock his phone with derpunlock.sbf. When he flashed full 198_7 sbf, everything was fine. Once he tried to unlock different way, that sleep of death was gone.
But this looks like the cause of your problem could be somewhere else.
Click to expand...
Click to collapse
I unlocked using the derpunlock and fastboot method for CWM. It went off without a hitch. Switched back to the Photon to see if the SOD's still occur. I'll keep this thread updating to see if the problem gets resolved. Thanks for the help!
Many helpful people here .
Thanks to all, I might get a photon soon
Buttery Smooth THS15 Deviled
lord dredd said:
Many helpful people here .
Thanks to all, I might get a photon soon
Buttery Smooth THS15 Deviled
Click to expand...
Click to collapse
We try
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
jaawerth said:
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
Click to expand...
Click to collapse
Exact same thing happened to me last evening...except I'm rooted with S-off.
grimmkt said:
Exact same thing happened to me last evening...except I'm rooted with S-off.
Click to expand...
Click to collapse
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
jaawerth said:
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
Click to expand...
Click to collapse
Sounds good! let us know!:good:
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
I can't get the phone to connect in fastboot. I keep getting a "driver failed to load" type error when I plug in the USB...the device is never visible.
Worked like a charm! The download took awhile, but once I had it downloaded it was easy.
For others searching for this issue:
Once you have the RUU, just install Android Development tools (specifically fastboot) and enter
>fastboot oem rebootRUU
>fastboot flash install IMAGEFILE.ZIP
Terminal/command prompt on the computer side told me it was finished but the phone was stuck at the very end of the progress bar. I waited a while few minutes, and when it didn't move I risked doing a
>fastboot reboot
and we were good to go.
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
jaawerth said:
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
Click to expand...
Click to collapse
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
jaawerth said:
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
Click to expand...
Click to collapse
It's a known hardware issue in the DNA. When they give you a new Sim tray it's thicker and it holds the Sim card in place better resulting with no more errors.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
:cyclops:hi guys, first of all thank you because you have saved me many times in the past just by reading through the forums. but this time
nothing seems to help me, i have a htc one m8 from sprint, and i tried to root it and install a custom room. And i did rooted now my device
shows tempered and bootloader is unlocked. I used twrp for the custom recovery later i tried to install android revolution one 4.0
and did not work but not only that i erase the partition of the phone so i soft bricked and my phone end up stuck on the boot loader not even
twrp will work :crying:and i try to repair the partition by using some comands that i found, but my phone was not getting recognized by adb just fastboot.
After a day i try a different custom recovery philz. and that one worked so i was able to enter to recovery, and i don't know why but when im inside the recovery my phone gets recognize by adb. I try to repair the partition, but since i have to grant access on the phone is not able to finish. so i tried to install
different rooms such as viper, badseed and it goes through the set up, but when it finish it just gets stuck on the boot loader again. I been trying
to install the stock room but i haven't been able to find it, i found a link in many different forums but the links are broken i been dealing with this
issue for over 5 days and don't know what to do. i will really apreciate if someone cuold help me please forgive me if you don't understand me but
english is not my native lenguage, so i don't speak it very well. also i'm a noob on rooting so i may not know a lot by the way my phone is s-on. help will be
really appreciate.
If you are S-On, when flashing a rom, it will not be able to automatically flash the kernel (boot.img) unless it specifically states in the OP it does by the developers. Most of the time, you'll just need to extract the boot.img and place it in the folder you have fastboot, then when connected in bootloader / fastboot mode run this : fastboot flash boot boot.img
after you flash the rom. Just boot into it right after, flash, and the just type : fastboot reboot
Should be good to go. FYI : adb isn't intended to work in bootloader and fastboot doesn't work in recovery. Nothing wrong there.
Sent from over there...
es0tericcha0s said:
If you are S-On, when flashing a rom, it will not be able to automatically flash the kernel (boot.img) unless it specifically states in the OP it does by the developers. Most of the time, you'll just need to extract the boot.img and place it in the folder you have fastboot, then when connected in bootloader / fastboot mode run this : fastboot flash boot boot.img
after you flash the rom. Just boot into it right after, flash, and the just type : fastboot reboot
Should be good to go. FYI : adb isn't intended to work in bootloader and fastboot doesn't work in recovery. Nothing wrong there.
Sent from over there...
Click to expand...
Click to collapse
thank for the help and i did as you said i install viper it finish a soon as it finished the phone reboot and went to bootloader i extract the boot.img from the zip and put it on the fastboot folder flash it and it said okay then i reboot the device and again just got stock on the bootloader im going to try to install android revolution and do the same thing but i almost sure is going to do the same thing. any other advice that you can provide me i will really appreciate it
and thanks again for the help.
update
just and update i did try also with android revolution and still no luck :crying:any help will be really appreciated:cyclops:
Can you post the link to the roms you are trying to load? I'm wondering if you aren't try to flash ones not for the Sprint M8? I don't see the ARHD rom in the forum for your phone...
es0tericcha0s said:
Can you post the link to the roms you are trying to load? I'm wondering if you aren't try to flash ones not for the Sprint M8? I don't see the ARHD rom in the forum for your phone...
Click to expand...
Click to collapse
thanks for the help first of all i have try this ones
ViperOne_6.0.0
Bad_Boyz_Sprint_ONE_KitKat_v1.2
BadSeed_Sixth_Sense_RLS2.1
Sprint_M8_1.12.651.17_system_dump
SENSE_STOCK_ROOTED_VZW_M8
Android_Revolution_HD-One_M8_4.0_ART
this are the ones, thank for the help again and i soon as we go through this im going to give you a donation for the big help
homar_80 said:
thanks for the help first of all i have try this ones
ViperOne_6.0.0
Bad_Boyz_Sprint_ONE_KitKat_v1.2
BadSeed_Sixth_Sense_RLS2.1
Sprint_M8_1.12.651.17_system_dump
SENSE_STOCK_ROOTED_VZW_M8
Android_Revolution_HD-One_M8_4.0_ART
this are the ones, thank for the help again and i soon as we go through this im going to give you a donation for the big help
Click to expand...
Click to collapse
Well, I definitely see a couple issues with that list...
The Viper 6.0.0 should be this one: http://forum.xda-developers.com/showthread.php?t=2334294 Which is for the International M7.
The Bad Boyz rom you posted should be the one from here: http://forum.xda-developers.com/showthread.php?t=2635051 - This is for the M7 version.
The BadSeed rom should be the one posted here: http://forum.xda-developers.com/showthread.php?t=2694471 - Also for the M7 (hence the M8 *PORT* in the title thread.
Now, HTC was stupid for giving the new phone the same name, I'll give you that, and XDA doesn't have it set to really filter well between the 2 forums, BUT stuff like the date posted could have been a give-a-way as well. But honest mistakes for sure. So, how to fix from here since your partitions are probably thoroughly hosed...? Hmm. Since I don't think there is an official Sprint RUU, that will be tricky. You will most likely need to get a hold of a very experienced HTC dev like the one's whose roms you were trying to use. The Viper, Bad Boyz, and BadSeed dev teams are all very good at most everything HTC. Another option is the developer : Captain_Throwback. He is very knowledgeable about HTCs from top to bottom and seems to be pretty helpful. Your casual helper will most likely not be able to provide as detailed help as you would need in this situation.
The forums you want to hang out in for your phone are here: http://forum.xda-developers.com/sprint-htc-one-m8
es0tericcha0s said:
Well, I definitely see a couple issues with that list...
The Viper 6.0.0 should be this one: http://forum.xda-developers.com/showthread.php?t=2334294 Which is for the International M7.
The Bad Boyz rom you posted should be the one from here: http://forum.xda-developers.com/showthread.php?t=2635051 - This is for the M7 version.
The BadSeed rom should be the one posted here: http://forum.xda-developers.com/showthread.php?t=2694471 - Also for the M7 (hence the M8 *PORT* in the title thread.
Now, HTC was stupid for giving the new phone the same name, I'll give you that, and XDA doesn't have it set to really filter well between the 2 forums, BUT stuff like the date posted could have been a give-a-way as well. But honest mistakes for sure. So, how to fix from here since your partitions are probably thoroughly hosed...? Hmm. Since I don't think there is an official Sprint RUU, that will be tricky. You will most likely need to get a hold of a very experienced HTC dev like the one's whose roms you were trying to use. The Viper, Bad Boyz, and BadSeed dev teams are all very good at most everything HTC. Another option is the developer : Captain_Throwback. He is very knowledgeable about HTCs from top to bottom and seems to be pretty helpful. Your casual helper will most likely not be able to provide as detailed help as you would need in this situation.
The forums you want to hang out in for your phone are here: http://forum.xda-developers.com/sprint-htc-one-m8
Click to expand...
Click to collapse
thanks so much for the help im learning a lot like what is a RUU and as you said i try to look for one no luch anyhow i have a doom question how do i get a contact with them how can i get the help from the ones that you mention im sorry but so far i been using xda to read through the forums this is actually my first time posting a problem i will really appreciate the help thank you.
homar_80 said:
thanks so much for the help im learning a lot like what is a RUU and as you said i try to look for one no luch anyhow i have a doom question how do i get a contact with them how can i get the help from the ones that you mention im sorry but so far i been using xda to read through the forums this is actually my first time posting a problem i will really appreciate the help thank you.
Click to expand...
Click to collapse
1 of 2 ways : post on a thread they have up, or click on their name on the left pane of the forum thread and it should give you options to Private Message the member. Keep in mind, many developers are busy people and some of them just ignore their PMs because they get so many for simple questions. Yours is certainly not gonna be the easiest fix. I would suggest to maybe start here: http://forum.xda-developers.com/showthread.php?t=2696652
es0tericcha0s said:
1 of 2 ways : post on a thread they have up, or click on their name on the left pane of the forum thread and it should give you options to Private Message the member. Keep in mind, many developers are busy people and some of them just ignore their PMs because they get so many for simple questions. Yours is certainly not gonna be the easiest fix. I would suggest to maybe start here: http://forum.xda-developers.com/showthread.php?t=2696652
Click to expand...
Click to collapse
thank you so much i'll do that, i really appreciate your help and your time
homar_80 said:
thank you so much i'll do that, i really appreciate your help and your time
Click to expand...
Click to collapse
No problem! Don't let this scare you away from trying to mod your phone later on. Just use this as a learning experience about the importance of reading. Lots.
hay
+D
es0tericcha0s said:
No problem! Don't let this scare you away from trying to mod your phone later on. Just use this as a learning experience about the importance of reading. Lots.
Click to expand...
Click to collapse
thank you for everything and i will keep trying also i have another htc one but the first generations i will mod it as well as soon as im done with this one jejeje
and believe me that i been reading for day trying to find a solution to my problem but hopefully soon with some help can be able to do it and if you want i can post and update in here of how finally i was able to fix it... thanks
First off, this should be posted in the Sprint M8 Q&A forum.
Next, I assume you have a stock nandroid, as that's the first thing everyone should do after getting a custom recovery installed on the device. So start by restoring that. If for some reason you don't have that, I believe there's one floating around in the "Stock ROM or any" thread in Sprint M8 General or Q&A.
Once you can boot up the device, you should be good to proceed to S-OFF and flash only ROMs specified for the Sprint M8 variant.
My pleasure. It's how I like to give back to the community. I have a ridiculous amount of experience with everything root, recovery, rom, mods, themes, apps, etc related after modding 100s of phones and tablets, but these type of issues require the next tier of experience when you're getting into semi uncharted territory due to how new the device is and that HTC hasn't released the official update utility for it. But yea, you should post back, just in case another member runs into the same problem and you can help point them in the right direction.
Captain_Throwback said:
First off, this should be posted in the Sprint M8 Q&A forum.
Next, I assume you have a stock nandroid, as that's the first thing everyone should do after getting a custom recovery installed on the device. So start by restoring that. If for some reason you don't have that, I believe there's one floating around in the "Stock ROM or any" thread in Sprint M8 General or Q&A.
Once you can boot up the device, you should be good to proceed to S-OFF and flash only ROMs specified for the Sprint M8 variant.
Click to expand...
Click to collapse
thanks for the quick help and yes i did create a back up of the phone but when i was trying to install the first custom room Android_Revolution_HD-One_M8_4.0_ART it ask me if i want to delete all data and i said yes. So my partitions of the phone i believe are screw up. I did look for Stock room i found many that were linking to the same file both the oex and deodex links were bronken and i haven't been able to find the one that i need that is kitkat 4.4.2 sprint. and i don't know what's next from were i am now.
homar_80 said:
thanks for the quick help and yes i did create a back up of the phone but when i was trying to install the first custom room Android_Revolution_HD-One_M8_4.0_ART it ask me if i want to delete all data and i said yes. So my partitions of the phone i believe are screw up. I did look for Stock room i found many that were linking to the same file both the oex and deodex links were bronken and i haven't been able to find the one that i need that is kitkat 4.4.2 sprint. and i don't know what's next from were i am now.
Click to expand...
Click to collapse
I'm not sure I understand. What does deleting all data have to do with your backup? Are you saying your backup got deleted? In that case, do what I said and find the one I referred to and restore that.
EDIT: http://forum.xda-developers.com/showthread.php?p=51624633
Captain_Throwback said:
I'm not sure I understand. What does deleting all data have to do with your backup? Are you saying your backup got deleted? In that case, do what I said and find the one I referred to and restore that.
Click to expand...
Click to collapse
He flashed 3 or 4 different roms that were for the M7 or not for his version of the M8. Pretty sure that the partitions are borked at this stage as properly flashing the correct M8 rom and fastboot flashing the boot.img has not gotten him out of trouble.
es0tericcha0s said:
He flashed 3 or 4 different roms that were for the M7 or not for his version of the M8. Pretty sure that the partitions are borked at this stage as properly flashing the correct M8 rom and fastboot flashing the boot.img has not gotten him out of trouble.
Click to expand...
Click to collapse
thanks i was looking for the words to explain that my English is really bad i apologize for that.
homar_80 said:
thanks i was looking for the words to explain that my English is really bad i apologize for that.
Click to expand...
Click to collapse
Did you see my post?
---------- Post added at 05:15 PM ---------- Previous post was at 05:11 PM ----------
Captain_Throwback said:
I'm not sure I understand. What does deleting all data have to do with your backup? Are you saying your backup got deleted? In that case, do what I said and find the one I referred to and restore that.
EDIT: http://forum.xda-developers.com/showthread.php?p=51624633
Click to expand...
Click to collapse
If restoring the above doesn't work, you can try this:
- Relock bootloader (fastboot oem lock)
- Download signed firmware zip from here. Flash via fastboot (fastboot oem rebootRUU, fastboot flash zip firmware.zip, fastboot reboot-bootloader)
- Unlock bootloader via HTCDev.
- Download TWRP Recovery from here and fastboot flash (fastboot flash recovery openrecovery-twrp-2.7.0.2-m8_whl.img)
- Download Stock Rooted ROM from here and flash via TWRP.