I'm having all kinds of trouble with my MT. I originally flashed CM7 from stock with CWM after wiping factory and cache. The flash errored out the first time, but worked the second time. The gapps install errored out so I just tried rebooting without stock google apps. The phone just booted to the Motorola logo and didn't go any farther. I let it sit for over 20 minutes and no go.
I had made a backup so I went back to CWM to restore the phone. Again, I did a factory and cache wipe, ran the restore, rebooted, but now the phone boots to Motorola logo, then reboots into CWM. So weird!
I have a theory that it has something to do with a hardware problem. When I try to flash another rom (besides cm7) the screen goes blank (no text) and then goes back to the root menu. I tried booting to CWM then plugging it in and removing the battery but after an varied amount of time the phone shuts off.
I've searched and searched and I can't find where anyone's had a problem like this and NOT been able to get the phone back. I'd like a solution, but I'd also like to know if i'm the only one who's had this problem!
thanks!
Never mind
I got it working! I tried a different battery in it and it worked! I'm not sure if it was the battery or I just did the right combination of things, but I'm glad to be back! But for anyone who is having the same issue here's what I did:
Running CWM 5.0.2.6
1. Wipe factory/cache/davlik
2. format sd card
3. shut down
4. use pc to copy stock nandroid backup from androidforums (google "stock triumph restore")
5. boot back to CWM,
6. restore the backup and reboot, should work
**IF you have md5 checksum error, use adb via usb to run these commands and immediately try to restore again:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
# exit
**Make sure to unmount the sd card before restore.
Again, I really don't know if it was battery or not, but I tried this before changing batteries and it didnt work!
But wait, there's more!
Ok, now that I'm able to get back to stock, I'm still unable to flash any custom roms. I wipe/factory reset, format /system, then install update from sd card. When I confirm the update, the screen goes blank (no text), then goes back to the main menu! It does this with any rom!
Any help?
dont think triumph is supported phone according to cwm ?
garrmack said:
Ok, now that I'm able to get back to stock, I'm still unable to flash any custom roms. I wipe/factory reset, format /system, then install update from sd card. When I confirm the update, the screen goes blank (no text), then goes back to the main menu! It does this with any rom!
Any help?
Click to expand...
Click to collapse
You want to choose zip from sd card. Not install update
Sent from my VS910 4G using xda premium
I knew I'd word something wrong
I meant to say that. I did install zip from sd.
garrmack said:
I meant to say that. I did install zip from sd.
Click to expand...
Click to collapse
Are you running the latest cwm?
Sent from my VS910 4G using xda premium
Yep, 5.0.2.6. I just tried CM7 .04 beta because I have a friend who flashed it successfully on his MT. When I ran it it said it was installing for maybe 4 seconds and then said complete. When I rebooted all I got was the Motorola logo.
I just got this phone. Is it possible that Motorola changed something with the hardware to make it not work?
I've managed to get CWM running a little more stable by replacing the boot.img file with the one from CM7, but all I get when I run the zip is this:
-- Installing /sdcard/CM7.zip
Finding update package...
Opening update package...
Installing update...
Install from sdcard complete.
that all takes about 6 seconds and I get just the motorola logo when I reboot.
It still goes blank (no text) when I try to flash any other rom (like stockROM) so something is definitely screwy.
I don't know if this has anything to do with it, but I have a friend with a Triumph who successfully flashed cm7. I looked at his phone and found that the model number on his is WX345 while mine is WX435. Maybe my version really does have issues with clockwork?
vizionforever said:
dont think triumph is supported phone according to cwm ?
Click to expand...
Click to collapse
I did notice that the Triumph isn't listed on Clockwork's site. It is, however, listed on xda. Maybe its not officially supported?
figured it out! It had something to do with the sd card. I was using a 16gb class 10 PNY card. I put the stock 2gb back in it and it worked like a charm. Don't know if it was a defective card or the phone/clockwork just didn't like it.
Bay PONY...Noticed that my pny class 10 16gb was slower(or just took longer to mount and search for media, cause it's bigger) than the 16gb samsung class 2 that came with my epic...Dunno; but glad to hear CWM works! now you can switch back cards
PS. what root method u use command line or gingerbreak?
vizionforever said:
PS. what root method u use command line or gingerbreak?
Click to expand...
Click to collapse
I've tried both. I like the gingerbreak b/c it adds superuser app for you. Both worked fine though...
But since I installed CM7 I didn't need to root it first.
Hi,
I'va had CM7 a10 flashed on my Sensation for a few days. A couple of days ago I've decided to get back to Stock ROM, and then the problems started. Before installing CM7 everything was fine. After restoring my backup from before flashing CM7 weird things started to happen (apps dissapearing, settings changing on their own, hangs, and other stuff). So I've done a SuperWipe a few times, and flashed a completely new Stock ROM via USB using: RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed file. Then I've done a few factory resets, just in case. But still weird things are happening (eg. now I have a clean phone - once again - and trying to setup the sync options and the options app hangs everytime. and installing something from market is like praying for a miracle). I've tried doing factory reset, clear cache/dalvik (but with dalvik CWM recovery says that the partition or files wasn't found). Don't know what to do. Does anyone have any ideas ?? Please help. Phone worked fine before, and after CM7 everything is f*cked up
Wierd, looks like you've tried everything I could think of while reading the post.
Do you still have a nandroid backup of CM7, if so does that work if you restore ?
Can you use ADB to get to the phone ? If so you could check some things from there.
When you installed the RUU from the PC, did it install without errors ? Presumably you had to re-install CWM after that.
CM7 nand backup works fine after restore.
I can use ADB to comunicate with the phone.
No errors while updating RUU.exe / CWM recovery flashed without problems also after that.
I think that there's something screwed up with the file permissions.
I've downloaded and installed about 20 apps since the last HR, and now I have about 40 apps more queued in Market, and as before the downloads are stuck every 1-2 apps. Then I have to restart to CWM recovery and run fix permissions. After that another 1-2 apps will download and get stuck again, and so on...
Anyone has any ideas what the hell is going on ? Because my I'm getting more then irritated by this, and beggining to think that the best solution will be to send my phone flying through the window.
A few questions first.
What country are you in?
Who is your carrier?
What version did your phone originally come with? I believe 1.5xxxxx RUU was released recently, but I could be wrong.
Did you ever change your CID?
Have you ever flashed a new radio and RIL?
Did you copy all of the data from your SD card to your computer, then format your SD card using the phone?
Answer these questions and try the SD card thing, then report back. I may be able to help.
Poland.
T-Mobile (Sensation) / Play Mobile (Gio)
Don't remeber what version my Sensation originally came with - I have a 1.50.401.1 RUU that I'm flashing with currently.
Yes, I've changed CID to 11111111 some time ago, but I'm back to original HTC__001 now.
No I haven't changed my radio or RIL.
I've tried formatting the SD card using the phone, my laptop, my linux NAS, my other phones.
The weird thing is that yesterday all of this was progressing. It came to a point that after a factory reset or even a whole ROM reflash nothing would install (not even Market update). And this also started to happen on my Samsung Gio. So after very very very frustrating evening, and part of the night I gave up. And in the morning it was still the same (on both my android phones). But now things are starting to work (updates/installs). So I think I'm going to blame the whole thing on Google and Market. I'll see what happens while I'll install all my apps in the next few hours.
Still have to restart the phone every 1-3 apps installed. This is driving me crazy
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
At this point, i would suggest to do a full wipe (clear data/factory reset, caches and also format system under storage and mounts). Then flash your flavor of CM7 and while still in CWM, flash the kernel of your choice, DON'T REBOOT, but clear cache/dalvik. Reboot, let it sit for a while and you should be good.
Sent from my LG-P999 using xda premium
Luriden said:
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Click to expand...
Click to collapse
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after that you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Instaling custom kernel instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
ratza66 said:
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Click to expand...
Click to collapse
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Make sure you downloaded his CM7 version and not Stock kernel.
Luriden said:
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Click to expand...
Click to collapse
You welcome, I've added info on how to install custom kernel too
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Luriden said:
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Click to expand...
Click to collapse
You can't install custom kernel on nightly release. Use RC 7.2 and yes do the rom recovery and back it up so the next time you can just restore to any rom that works on your phone.
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Luriden said:
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Click to expand...
Click to collapse
I Think you are missing a one step, Wipe Dalvik. Ok let start from the begining,
First restore your phone to stock, let it boot. Root your phone and install CWM. Install CM7.2 RC rom and let it boot. Go back to the CWM and follow this instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
all these steps are important. I was using CM 7.2 RC with Faux's kernel without any problem and it worked flawlessly
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Luriden said:
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Click to expand...
Click to collapse
Follow this guy on YT, you will find everything there
http://www.youtube.com/watch?v=fxMnnarHaOU
Installing CM7 tutorial
http://www.youtube.com/watch?src_vi...id=annotation_334516&feature=iv&v=Cy9on64jAZs
This one is even better
http://www.youtube.com/watch?v=vUaWXM8GwUI
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Luriden said:
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Click to expand...
Click to collapse
No chance. Nothing will be left over when you wipe your phone. Your SD card is only accessed when you tell CWM to do so. Take your phone back to stock. Do it again this time try either a froyo rom or ICS rom. Then go back wipe everything and install CM7. Sometimes you have to take the long way. after flashing my phone a bazzilion time I learned this the hard way when I couldnt load EB ICS anymore. Had to run GB to get to ICS. Try it in reverse or from a step below and it should go through fine. IF it doesn't, you might have to use ICS instead, which may be stuttery, but works damn well.
DupleX01 said:
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
Click to expand...
Click to collapse
I'm wondering why he still has the issue. YOU CLEAN CACHE BEFORE FLASHING KERNEL/ROM UPDATES!!!
Sent from my LG-P999 using xda premium
For God sake, just flash a random ROM to get access to inside your phone.
1. DIAG your phone OFFLINE with v21e baseband (phone will automatically restart)
2. Let it stay for 5mins after that
3. Use your phone for 15mins
4. Root using 1Click
5. Install CWM
6. Install your ideal ROM + GAPPS (if needed) via CWM
7. Reboot
8. Go outside your living room and watch TV for at least 15mins
9. Reboot your phone into CWM and flash your ideal kernel
10. Enjoy!!!
You better know which ROM/kernel to choose from. Period.
How to upgrade/downgrade your baseband? Do some search, please!
Sent from my LG-P999 using xda premium
I'll do a flash of Froyo or ICS and possibly some baseband research tomorrow. Considering my luck getting a simple rom flash to work, I don't feel too comfortable dealing with the baseband.
A friend was brave enough (somehow) to let me root and install CM7 on his phone, he has the same phone as mine. I got CM7 7.2 RC and Faux's DM UV working like a dream on my first try. Tried it on my phone after recovering it, same problem. So it's a problem that exists deeper on my phone, not with my methods.
The NAND restores for GB and Froyo give me MD5 checksum errors, and the stock zipped rom of GB gives me an installation failed error, so I'm thinking a zipped Froyo rom won't work either, but it might be worth a shot.
Tried Weapon and MIUI too. No go. If I don't get stuck at the blue LG logo, then I'm stuck in a loop between the two LG logos or stuck at a flashing black screen. 8/10 times though it's the blue LG, I think the other errors may have actually been me forgetting to wipe my cache when I was flustered.
I'll try ICS, and hopefully won't get to a point where I have problems installing things I used to be able to, since that seems to be the pattern. After that I finally give up.
I FIGURED IT OUT! Well, sort of. For the hell of it, I downloaded CM7 7.1.0.1 through Rom Manager and it installed fine. It downloaded it to my internal SD, so I hooked it up to my PC to copy the 7.2.0 RC1 to my internal SD and tried installing. No go.
So I went on my phone's web browser and redownloaded 7.2.0 RC1 that way directly to the phone. It works. So somehow, roms I copy from my PC to the phone appear to not work, yet apps and kernels still do. I'm running CM7 7.2.0 RC1, downloaded through my phone's web browser, with Faux's DS UV kernel, copied from my computer. After four days, I finally found a workaround, so I'll stick to it. Whatever works, I guess. I can try reinstalling my USB drivers, but I can probably get by with a combination of the phone's web browser and ES File Manager w/ LAN if need be.
Hi all
I hope that I am posting in the correct place
I need help with my Galaxy S3 SGH-T999
Recently the phone died on me, it was stock rom and with the updates through some of the apps, the phone stopped working correctly. I don't use the phone for making calls, etc, but need it for pictures and a few other apps. The phone is from T-mobile.
I tried to reset the phone and that worked until all the updates were back on and then back to the same problem.
So I decided to put on a custom rom on the phone.
I have tried the following roms:
cm-14.1-20161225-NIGHTLY-d2tmo
I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME
RevolutionaryS5-V3
Slim-d2tmo-6.0.1.alpha.0.1-UNOFFICIAL-20160516-1346
I first installed CWM recovery and then transferred the roms over to the external sd car (also the internal card), went to boot manager (vol up) and installed the files.
It looked like the installation worked but when selecting reboot, the phone would not come back on.
I then loaded up Kies and reset the phone back to factory defaults and only then does the phone load back up after reboot.
Every time I try the custom rom - I run into the same problem
At first I thought the phone was bricked and found info about the jtag and then found something about using an SD card with the following image installed on it - tmobile-T999_4.3_debrick
With the SD card in the phone I can boot to either menus and also able to get the phone to boot to the slim-d2tmo rom. But when I pull the SD card, the phone won't boot. Nothing, no power, nada
I am not sure what I did wrong, followed the direction on the site and thought I did it correctly.
Not sure if I deleted some file, or partition needed or what. I would greatly appreciate some help with this.
Also I would like a custom rom that is stable and fast. I don't need all the bells and whistles but one thing I would like and that is for the camera to be able to take pictures using voice. I know the stock rom allows for this. Not essential but preferred.
Please help with detailed instructions.
Thanks in advance.
After writing this I just loaded up T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar and managed to get the phone back up and running. Then tried the cm-14.1-20161225-NIGHTLY-d2tmo - which I kinda like but it will not boot up without the SD card in. I can manage to get the phone booted with the SD card and get into the new custom rom, but I have to keep pulling the battery, insert the SD card and then try to boot. Don't think it should work like this
Please help.
kouger1 said:
Hi all
I hope that I am posting in the correct place
I need help with my Galaxy S3 SGH-T999
Recently the phone died on me, it was stock rom and with the updates through some of the apps, the phone stopped working correctly. I don't use the phone for making calls, etc, but need it for pictures and a few other apps. The phone is from T-mobile.
I tried to reset the phone and that worked until all the updates were back on and then back to the same problem.
So I decided to put on a custom rom on the phone.
I have tried the following roms:
cm-14.1-20161225-NIGHTLY-d2tmo
I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME
RevolutionaryS5-V3
Slim-d2tmo-6.0.1.alpha.0.1-UNOFFICIAL-20160516-1346
I first installed CWM recovery and then transferred the roms over to the external sd car (also the internal card), went to boot manager (vol up) and installed the files.
It looked like the installation worked but when selecting reboot, the phone would not come back on.
I then loaded up Kies and reset the phone back to factory defaults and only then does the phone load back up after reboot.
Every time I try the custom rom - I run into the same problem
At first I thought the phone was bricked and found info about the jtag and then found something about using an SD card with the following image installed on it - tmobile-T999_4.3_debrick
With the SD card in the phone I can boot to either menus and also able to get the phone to boot to the slim-d2tmo rom. But when I pull the SD card, the phone won't boot. Nothing, no power, nada
I am not sure what I did wrong, followed the direction on the site and thought I did it correctly.
Not sure if I deleted some file, or partition needed or what. I would greatly appreciate some help with this.
Also I would like a custom rom that is stable and fast. I don't need all the bells and whistles but one thing I would like and that is for the camera to be able to take pictures using voice. I know the stock rom allows for this. Not essential but preferred.
Please help with detailed instructions.
Thanks in advance.
After writing this I just loaded up T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar and managed to get the phone back up and running. Then tried the cm-14.1-20161225-NIGHTLY-d2tmo - which I kinda like but it will not boot up without the SD card in. I can manage to get the phone booted with the SD card and get into the new custom rom, but I have to keep pulling the battery, insert the SD card and then try to boot. Don't think it should work like this
Please help.
Click to expand...
Click to collapse
You did the right thing with the SD card, the issue with it not booting with SD card removed is not an issue, that's the way its supposed to work. After restoring boot with the SD card you've got to do a few other steps to correct the device so that it boots without SD card and then you've got to return the SD card to normal function to use it as storage again.
There's a thread in the Verizon Galaxy S3 I535 forum for unbricking with the SD card and the further instructions to restore full functional boot without SD card.
Sent from my SCH-I535 using Tapatalk
I appreciate the help. This should work on my phone even thought it is a T-Mobile and it is a SGH-T999 ?
Any chance you know of the link to fix the booting issue?
I really need to get this sorted out. I am about to trash the phone and get some cheap $80 best buy special just to use the apps I need.
kouger1 said:
I appreciate the help. This should work on my phone even thought it is a T-Mobile and it is a SGH-T999 ?
Any chance you know of the link to fix the booting issue?
I really need to get this sorted out. I am about to trash the phone and get some cheap $80 best buy special just to use the apps I need.
Click to expand...
Click to collapse
The method is the same, you just use your debrick.img for your device instead of the Verizon debrick.img.
https://forum.xda-developers.com/showthread.php?t=2581166
Sent from my SCH-I535 using Tapatalk
So I feel like such a dufus.
I think I know what I did wrong. After going back and forth reading everything, which all looked like what I had originally, I realized that everyone was talking about loading the zip files from the sd card. Thought I did this, but what I was doing was loading them from the external SD card.
So after having put the stock rom back on the phone (and basically gave up) I decided this morning to try one last time.
I downloaded:
OCT-N-WEEKLY-20170127-2232-d2tmo
open_gapps-arm-7.1-micro
Connected the S3 to my PC and copied both files to the phone. Did not have the external SD card plugged in.
Then went to boot menu (vol up) and cleared the cache, davik and data. Installed from zip (local phone this time) and within 10 minutes (or less) the phone was up and running without any issues.
BAM - awesome.
Seemed too good to be true but worked like a charm.
I wonder if that was the problem with any of the other roms I tried?
Anyway, thanks to all for your help.
kouger1 said:
So I feel like such a dufus.
I think I know what I did wrong. After going back and forth reading everything, which all looked like what I had originally, I realized that everyone was talking about loading the zip files from the sd card. Thought I did this, but what I was doing was loading them from the external SD card.
So after having put the stock rom back on the phone (and basically gave up) I decided this morning to try one last time.
I downloaded:
OCT-N-WEEKLY-20170127-2232-d2tmo
open_gapps-arm-7.1-micro
Connected the S3 to my PC and copied both files to the phone. Did not have the external SD card plugged in.
Then went to boot menu (vol up) and cleared the cache, davik and data. Installed from zip (local phone this time) and within 10 minutes (or less) the phone was up and running without any issues.
BAM - awesome.
Seemed too good to be true but worked like a charm.
I wonder if that was the problem with any of the other roms I tried?
Anyway, thanks to all for your help.
Click to expand...
Click to collapse
I don't know what you were having issues with but I've always flashed my ROMs from extsdcard. Unless I'm missing your meaning.
Sent from my SCH-I535 using Tapatalk
Then maybe it were the roms I was using. All the roms I tried would not boot my phone after installation. I had to add the following file to my external SD card -tmobile-t999_debrick
This was the only way I could get the phone to boot back up after I installed the roms.
Or maybe I was using the wrong roms - I have no idea.
I guess my thought process was not correct and that you don't have to put the roms on the internals storage and can use the external sd card to install the roms?
kouger1 said:
Then maybe it were the roms I was using. All the roms I tried would not boot my phone after installation. I had to add the following file to my external SD card -tmobile-t999_debrick
This was the only way I could get the phone to boot back up after I installed the roms.
Or maybe I was using the wrong roms - I have no idea.
I guess my thought process was not correct and that you don't have to put the roms on the internals storage and can use the external sd card to install the roms?
Click to expand...
Click to collapse
Typically, you install custom recovery then root then place new ROM on extsdcard then flash the ROM in recovery from extsdcard. Its actually recommended to keep your ROM zips on external if you have it instead of internal because if internal gets wiped or corrupted then you've lost your ROM zip. It's also recommended to create and store your nandroid backups on extsdcard.
Sent from my SCH-I535 using Tapatalk