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.
Related
Hey guys so I'm pretty tech savvy and i know my way around this phone but something weird's been happening. I had CM 4.2 on my Mytouch3G. I tried applying a theme which made it not boot up anymore(bootloop).
I did make a nandroid backup before but when i tried restoring with it, it keeps getting stuck at the green mt3g screen or at the second loading screen. I've tried flashing the rom again but gets stuck at the same place. If I just install the htc 1.6 update it works fine. But when I go to apply the CM 4.2 update it gets stuck again. I have wiped a million times, and fixed ext system also a bunch of times. I have also unrooted also by applying sappimg.nbh and starting over. Rooted, tried again, but nothing, still getting stuck at the loading screen. I have gotten it a couple times to go all the way to the home screen but i get com.android.phone force close.
Also i've tried going from stock htc 1.6 to CM 4.1.99 and up, not just straight to CM 4.2 so i don't know what to do.
Any help appreciated!
I seem to be having this problem as well.
Phone just freezes at MT3g loading screen.
4.1.9.2 seems to load fine, however 4.2.1 flashes properly, but phone just sits at green loading screen.
charkosh said:
I seem to be having this problem as well.
Phone just freezes at MT3g loading screen.
4.1.9.2 seems to load fine, however 4.2.1 flashes properly, but phone just sits at green loading screen.
Click to expand...
Click to collapse
Maybe a mytouch issue? Hopefully we can get some help.
lupascu.marius said:
Maybe a mytouch issue? Hopefully we can get some help.
Click to expand...
Click to collapse
You didnt say the steps you took to flash it. Did you do the step by step instructions on Cyan's OP? You cant just flash it like a normal ROM you have to do what he says on his post. I followed the steps and my MT3G works fine with it.
bluecluenj said:
You didnt say the steps you took to flash it. Did you do the step by step instructions on Cyan's OP? You cant just flash it like a normal ROM you have to do what he says on his post. I followed the steps and my MT3G works fine with it.
Click to expand...
Click to collapse
But i did say the steps...i first flashed the htc recovery image like it CM said to do. I even said in the post that i already had cm 4.2 on my phone but had to reflash after a theme froze my phone at the boot screen. I know its a different install process compared to any other rom.
Make sure you wipe before applying rom
Mr Bill Florida said:
Make sure you wipe before applying rom
Click to expand...
Click to collapse
Do people even take time to read the original post, or do they just blurt out things that sound helpful? I said towards the middle of the post that i've wiped a million times and also tried fixing ext filesystem. I appreciate anyone trying to help but please read my post carefully!
I have the same problem guys, but oly with 4.2.3.1
http://forum.xda-developers.com/showpost.php?p=4851283&postcount=3677
i HAD a similar problem when i went to 4.1.999 the first time but i fixed it.
i prefer amon ra's recovery 1.2.3g. i wiped the file system AND cache. then i did the 1.6 update followed immediately with the CM update. i rebooted and let it load up completely, then rebooted into recovery again and applied the new theme.
i actually went through the process a couple times before it worked flawlessly. it may have been a different problem though, since i was getting past the mytouch splash and about 10 seconds into the android splash before it would freeze.
jayzusfk said:
i HAD a similar problem when i went to 4.1.999 the first time but i fixed it.
i prefer amon ra's recovery 1.2.3g. i wiped the file system AND cache. then i did the 1.6 update followed immediately with the CM update. i rebooted and let it load up completely, then rebooted into recovery again and applied the new theme.
i actually went through the process a couple times before it worked flawlessly. it may have been a different problem though, since i was getting past the mytouch splash and about 10 seconds into the android splash before it would freeze.
Click to expand...
Click to collapse
Thats a good idea...i'll try amon ra's recovery image and see if there's different results. Will post back soon.
lupascu.marius said:
Thats a good idea...i'll try amon ra's recovery image and see if there's different results. Will post back soon.
Click to expand...
Click to collapse
So i tried everything from scratch but with amon ra's rec image this time. It gets passed the first boot screen and right after the second android screen it goes straight to a black screen. Have tried a few variations of installing and same thing happens everytime...This blows, i'm so stuck.
lupascu.marius said:
So i tried everything from scratch but with amon ra's rec image this time. It gets passed the first boot screen and right after the second android screen it goes straight to a black screen. Have tried a few variations of installing and same thing happens everytime...This blows, i'm so stuck.
Click to expand...
Click to collapse
Quick update for anyone with any ideas. I finally got it to boot up and it runs great except for two things I've notices so far. When i try to add widgets nothing pops up and when i go to settings the window comes up for half a second then goes away and back to home screen. Now what I did to fix it was partition the sd card which i was told is NOT necessary. Then after i got it to work i tried again with a sdcard that was NOT partitioned and it did the same thing again, black screen no-go. So it seems like if you don't partition the sdcard on some phones the phone freezes at a black screen. Keywords being "some phones". So for anybody who knows how to fix the widget and settings problems not opening, please help me....Thanks
lupascu.marius said:
But i did say the steps...i first flashed the htc recovery image like it CM said to do. I even said in the post that i already had cm 4.2 on my phone but had to reflash after a theme froze my phone at the boot screen. I know its a different install process compared to any other rom.
Click to expand...
Click to collapse
Actually if you have an MT3G I believe you don't flash the 1.6 recovery image, but flash the 1.6 ADP rom. That is what I did since I was already rooted but with AmonRa's donut rom, but wanted to give Cy a shot, and I had no problems flashing this HTC ADP 1.6 DRC83 , then reboot manually but while rebooting I pushed home fast while it was rebooting to get me to the recovery screen, then I just flashed Cy's 4.2.2 then I went to the market and downloaded his Cyanogen updater and checked for an update, then found the update 4.2.3.1 and downloaded that straight to my phone and then choose to reboot and it automatically installed 4.2.3.1 straight to my MT3G with no problems at all.
From Cyanogen:
Download: Android 1.6 Recovery Image. (This isn’t like a typical "recovery" image we know -- it’s simply HTCs version of an update.zip.)
* Magic32A and Magic32B users only: Download this HTC_ADP_1.6_DRC83_rooted_base.zip
lupascu.marius said:
Quick update for anyone with any ideas. I finally got it to boot up and it runs great except for two things I've notices so far. When i try to add widgets nothing pops up and when i go to settings the window comes up for half a second then goes away and back to home screen. Now what I did to fix it was partition the sd card which i was told is NOT necessary. Then after i got it to work i tried again with a sdcard that was NOT partitioned and it did the same thing again, black screen no-go. So it seems like if you don't partition the sdcard on some phones the phone freezes at a black screen. Keywords being "some phones". So for anybody who knows how to fix the widget and settings problems not opening, please help me....Thanks
Click to expand...
Click to collapse
I would go ahead and put Cy's latest back on your sd card, and also download the HTC_1.6_ADP rom if you have a MT3G (Magic 32B) or a Magic 32A and put that on your sd card. WIPE WIPE WIPE - I always wipe three times, and wipe cache also, then flash the 1.6 ADP rom then reboot but while it is rebooting hold down home to get back to recovery screen then apply Cy's on top of the 1.6 ADP rom.
I went ahead and just put Cy's 4.2.2 (instead of 4.2.3.1) on my sd card along with the HTC 1.6 ADP Rom and flashed the HTC 1.6 ADP rom first, then rebooted manually from the recovery screen, then quickly hold down home while rebooting to get back to recovery screen and applied any zip Cy4.2.2. Then when I signed in went to market to download Cyanogen Updater and set that up and then checked for updates and it found 4.2.3.1. I dowloaded that from my phone and then it was automatic from there, just asked if I wanted to reboot and apply and I said yes. Up and running with no problems so far....
mavsfan said:
I would go ahead and put Cy's latest back on your sd card, and also download the HTC_1.6_ADP rom if you have a MT3G (Magic 32B) or a Magic 32A and put that on your sd card. WIPE WIPE WIPE - I always wipe three times, and wipe cache also, then flash the 1.6 ADP rom then reboot but while it is rebooting hold down home to get back to recovery screen then apply Cy's on top of the 1.6 ADP rom.
I went ahead and just put Cy's 4.2.2 (instead of 4.2.3.1) on my sd card along with the HTC 1.6 ADP Rom and flashed the HTC 1.6 ADP rom first, then rebooted manually from the recovery screen, then quickly hold down home while rebooting to get back to recovery screen and applied any zip Cy4.2.2. Then when I signed in went to market to download Cyanogen Updater and set that up and then checked for updates and it found 4.2.3.1. I dowloaded that from my phone and then it was automatic from there, just asked if I wanted to reboot and apply and I said yes. Up and running with no problems so far....
Click to expand...
Click to collapse
That is the exact process i run thru. Sorry for the confusion, the reason i said htc recovery 1.6 is because thats what htc calls it. So i do have the htc 1.6 adp.....and i do wipe a lot also
This is probably a dumb question as I assume you would have mentioned it, but are there themes involved in any of your troubles or are you staying with stock 4.2.3.1? I only ask because I was having the same issue with the SECOND android splash crashing because I had tried to install a theme before booting into Cyanogen at least once.
I also don't think you should reboot after installing the 1.6 base like mavsfan was suggesting, though I'm not sure if it's related to your issues.
Try booting it up without an sdcard inserted. If it works that means it's your card. Card issues are very hard to diagnose and even harder to solve (other than reformat).
jayzusfk said:
This is probably a dumb question as I assume you would have mentioned it, but are there themes involved in any of your troubles or are you staying with stock 4.2.3.1? I only ask because I was having the same issue with the SECOND android splash crashing because I had tried to install a theme before booting into Cyanogen at least once.
I also don't think you should reboot after installing the 1.6 base like mavsfan was suggesting, though I'm not sure if it's related to your issues.
Click to expand...
Click to collapse
The problem i have is with the stock 4.2.3.1 not the themes...and i've also tried without rebooting after installing the 1.6 base and just go straight to applying the CM update
pascanu said:
Try booting it up without an sdcard inserted. If it works that means it's your card. Card issues are very hard to diagnose and even harder to solve (other than reformat).
Click to expand...
Click to collapse
Hey thanks for your suggestion, i have tried that, I've reformatted, I've tried different SD cards and nothing changed. I'm pretty sure the sd cards are good...
[SOLVED]Finally...
So for anyone having similar issues, here's what i did to finally get this working.
Apparently with Cyanogen's newest ROM's you HAVE to partition your sdcard, so the Rom will run on certain phones. I don't know if its all phones because there's only a few people that i've heard to have this problem. So here's the steps:
Things you will need(all these can be found in this forum)
1. Phone+sdcard
2. sappimg.nbh
3. FlashRecovery.apk
5. AmonRa's recovery image(has more options than CM's RecImg)
6. Htc ADP 1.6 stock donut rom
7. CM 4.2.3+
8. A theme(optional)(check out the Eclair 2.0 theme)
Starting from scratch
1. a. Put sappimg.nbh on sd card and turn the phone off.
b. Turn phone on by holding VOLUME DOWN+POWER
c. Apply the stock sapphire image and boot up to home screen.
2. a. Now put FlashRec.apk and AmonRa's recovery image on sdcard.
b. Install a file manager like Astro and install FlashRec.apk
c. Now open it and click Backup Recovery Image.
d. Now erase whats in the box and type /sdcard/name.of.recoveryimage.img
e. Yes you do have to type .img after the recovery image name.
f. Then click flash.
3. a. Now put the HTC ADP 1.6 Rom and CM 4.2.3+ Rom on the sdcard.
b. Reboot into recovery by holding HOME+POWER.
c. Now partition your sdcard by selecting it from the menu(the one that says +swap)
d. Now convert ext2 to ext3. After that I did:
4. a. Wipe, format ext3, wipe
b. Flash HTC ADP 1.6
c. Wipe, format ext3, wipe again.
d. Flash CM 4.2.3+
e. Wipe, format ext3, wipe one more time
f. Reboot, now it should work, give it some time to boot up.
Adding the theme
1. Make a nandroid backup before starting to save you the hassle.
2. Put your theme.zip on sdcard and reboot in recovery again.
3. Choose apply any zip and choose the theme from the list.
4. Reboot once its done and enjoy.
If anyone has any questions about anything here go ahead and reply or PM me. Have a good one guys, hope this helps anyone.
Oh and if you guys see any mistakes let me know so i can fix it, its pretty late right now
I’m hoping that someone may read this and have an idea of something to try. Or something I’m missing.
I’ve worked on and rooted multiple android phones and never once had an issue until the thunderbolt.
A friend has a thunderbolt that we previously rooted and all was working well until one day after a reboot the phone got stuck at the white HTC boot screen and then after rebooting a second time, the phone essentially “restored” a stored image of some sort. Now EVERY time you reboot the phone, it first boots and gets stuck at the HTC white boot screen, then after rebooting it a second time, it goes back to this exact same “stored image” state. If you change the desktop settings, remove and install apps and then reboot (twice), the apps you removed come back, the apps you downloaded are gone and the desktop goes back to this “stored” state.
I’ve tried re-rooting, unrooting, auto root, auto unroot, fix permissions via clockwork recovery as well as through rom manager…no matter what I do to this phone after It reboots (twice), it constantly goes back to the same “stored image”
Also, after flashing a PG05IMG.zip file through HBOOT, when the phone reboots its exhibits the same behavior..gets stuck at white HTC screen, then second boot brings the phone RIGHT back to the “stored image” state.
Any ideas or help appreciated!
i think i saw someone else with this. let me see if i can find post.
take the sd card out
put sd card into a computer
delete/rename PG05IMG.zip
put sd card back in phone
reboot
sublimaze said:
take the sd card out
put sd card into a computer
delete/rename PG05IMG.zip
put sd card back in phone
reboot
Click to expand...
Click to collapse
What I was going to say.
Are you leaving the PG05IMG.zip on the SD card?
sublimaze said:
take the sd card out
put sd card into a computer
delete/rename PG05IMG.zip
put sd card back in phone
reboot
Click to expand...
Click to collapse
I wish it were that simple!! Unfortunately its not a bad /sdcard/PG05IMG.zip file that is being loaded back onto the phone. I verified this by booting the phone without the sdcard at all.
have you unrooted and rerooted?
Also do you have anything setup with Ti Backup?
boostenmkiv said:
I wish it were that simple!! Unfortunately its not a bad /sdcard/PG05IMG.zip file that is being loaded back onto the phone. I verified this by booting the phone without the sdcard at all.
Click to expand...
Click to collapse
The problem your having is ROM related not radio related. The PG05IMG file should have nothing to do with it. You need to do a wipe/factory reset and flash a new ROM. With those problems I wouldn't trust possibly restoring a backup of a corrupted ROM
ScoobarSTI said:
have you unrooted and rerooted?
Also do you have anything setup with Ti Backup?
Click to expand...
Click to collapse
I attempted to unroot and even re-root, but NOTHING will take...no matter what I flash, the phone will ALWAYS revert back to this same image.
Ti backup is installed but only has a couple apps backed up
I would wipe everything and format system
Sent from my HTC ThunderBolt using XDA App
00negative said:
I would wipe everything and format system
Sent from my HTC ThunderBolt using XDA App
Click to expand...
Click to collapse
Via which method?
RootandBoot, unfortunately even trying to flash new ROMs result in the exact same result...boot to white htc, gets stuck..reboot phone once more and it goes back to this crap image.
I also did the factory reset and also all 3 wipes (data, cache, dalvik) in clockwork...I even ADB shell'd into the phone and deleted stuff from system...after the double reboot...its back!
boostenmkiv said:
RootandBoot, unfortunately even trying to flash new ROMs result in the exact same result...boot to white htc, gets stuck..reboot phone once more and it goes back to this crap image.
Click to expand...
Click to collapse
Very strange. Do you think the "stored image" is a nandroid backup?
boostenmkiv said:
Via which method?
RootandBoot, unfortunately even trying to flash new ROMs result in the exact same result...boot to white htc, gets stuck..reboot phone once more and it goes back to this crap image.
I also did the factory reset and also all 3 wipes (data, cache, dalvik) in clockwork...I even ADB shell'd into the phone and deleted stuff from system...after the double reboot...its back!
Click to expand...
Click to collapse
Format /system via CWM. Mounts and storage.
sublimaze said:
Very strange. Do you think the "stored image" is a nandroid backup?
Click to expand...
Click to collapse
Thats a good question. I don't think the person who owns this phone actually has ever done a backup via clockwork or through rom manager...and when i went into clockwork restore, there weren't any backups visible.
Yes, this is the most odd android problem i've tried to help fix!
cam30era said:
Format /system via CWM. Mounts and storage.
Click to expand...
Click to collapse
Format failed...tried remounting and unmounting..no go
If all else fails, go back to bone stock, reboot a few times & see if the "stored image" recurs
Sent from my ADR6400L using XDA App
sublimaze said:
If all else fails, go back to bone stock, reboot a few times & see if the "stored image" recurs
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Thats the problem...I've been trying to get the phone to stock...actually trying to get it to do anything at this point. As soon as I try to flash ANYTHING, it doesn't work.
That is the most bizarre behavior I've ever come across, and I've had 3 android phones. If you can't get it back to stock, then I have no idea what to try next. Have you tried the IRC channel?
Sent from my ADR6400L using XDA App
So i decied to go to carbon rom because my phone has been acting strange, YouTube would keep resigning in everything i would launch it, Random crashed and freezes and has just been acting up for no good reason. I was running CM 10.1 nightly and dont apply ant mods to it or anything like that becuase i like it simple.
When i flashed the rom i did it with gapps but they were not intalled when i boot, all i got was my SIM pin popup like i usualy get. So i re-flashed gapps and still no luck. So i said f*** it and found another build of it and copyed it to my SD Card and was going to flash it. Like i allways do i went to factory reset and all i got was a long log of cant remove lost+found and same happed when i tryed to wipe the system. and that didnt look good so i pulled the battery and booted recovery with the key press and it would get to teamwin screen but would reboot. Opened oden on my desktop, reflashed teamwin tar and that didnt help it. So i was lucky that i loaded the rom and i rebooted to recovery and am copying all my /data/media to a sdcard that i have
So can anyone give me some links to the 16GB PIT and all that jazz so i can get thing back up and running
And no i am not a n00b becasue i have been working with android and other phones long enough to know what i am doing
powercamg4 said:
So i decied to go to carbon rom because my phone has been acting strange, YouTube would keep resigning in everything i would launch it, Random crashed and freezes and has just been acting up for no good reason. I was running CM 10.1 nightly and dont apply ant mods to it or anything like that becuase i like it simple.
When i flashed the rom i did it with gapps but they were not intalled when i boot, all i got was my SIM pin popup like i usualy get. So i re-flashed gapps and still no luck. So i said f*** it and found another build of it and copyed it to my SD Card and was going to flash it. Like i allways do i went to factory reset and all i got was a long log of cant remove lost+found and same happed when i tryed to wipe the system. and that didnt look good so i pulled the battery and booted recovery with the key press and it would get to teamwin screen but would reboot. Opened oden on my desktop, reflashed teamwin tar and that didnt help it. So i was lucky that i loaded the rom and i rebooted to recovery and am copying all my /data/media to a sdcard that i have
So can anyone give me some links to the 16GB PIT and all that jazz so i can get thing back up and running
And no i am not a n00b becasue i have been working with android and other phones long enough to know what i am doing
Click to expand...
Click to collapse
I think this is what you are looking for. Follow the guide and you will be on stock, rooted, and unlocked.
http://forum.xda-developers.com/showthread.php?t=2046439
mapatton82 said:
I think this is what you are looking for. Follow the guide and you will be on stock, rooted, and unlocked.
http://forum.xda-developers.com/showthread.php?t=2046439
Click to expand...
Click to collapse
Iv been able to load a rom but now i cant write to the phone, i have now found a guide talking about unbricking it useing odin anf a nand erase all and thats not working eather, any story i can tell verizon so i can get a replacement today?
Update!
Iv been useing http://forum.xda-developers.com/showthread.php?t=1840030 to try to get my phone back and so far it has failed but i decied to switch computers, all my computers are now running windows 8 and i ws doing this on my development computer / server and then i switched to the last computer to have windows 7 next to my main computer and what do you know it worked, the nand erase worked and now its booting im sure i will have to re-unlock the bootloader and all but im happy now
I had just downloaded the latest firmware to upgrade to lolipop, I did a titanium backup, then a nandroid with TWRP.
Upon reboot I can only get to the default recover screen (The one with the android on the skateboard). I can boot into TWRP and have tried clearing cache and delvik cache, and now doing a factory reset but I'm still having the problem. sometimes when rebooting from TWRP the phone boots to the lock screen (or to setup screen after factory reset), then a few seconds later reboots back to the screen with the android on the skateboard.
I haven't even started installing the new firmware, all I did was backup with TWRP and it seems to have semi bricked the phone.
I also tried restoring the backup and I get an error "E:\ No Partition selected for restore."
Justintoxicated said:
I had just downloaded the latest firmware to upgrade to lolipop, I did a titanium backup, then a nandroid with TWRP.
Upon reboot I can only get to the default recover screen (The one with the android on the skateboard). I can boot into TWRP and have tried clearing cache and delvik cache, and now doing a factory reset but I'm still having the problem. sometimes when rebooting from TWRP the phone boots to the lock screen (or to setup screen after factory reset), then a few seconds later reboots back to the screen with the android on the skateboard.
I haven't even started installing the new firmware, all I did was backup with TWRP and it seems to have semi bricked the phone.
I also tried restoring the backup and I get an error "E:\ No Partition selected for restore."
Click to expand...
Click to collapse
You flashed twrp either by twrp manager or allowed flashify to download the image for you. Try flashing the firmware zip I posted in tigerstowns thread that has twrp in it. If that doesn't work you will need to ruu and then install twrp and restore. Do not use twrp manager.
dottat said:
You flashed twrp either by twrp manager or allowed flashify to download the image for you. Try flashing the firmware zip I posted in tigerstowns thread that has twrp in it. If that doesn't work you will need to ruu and then install twrp and restore. Do not use twrp manager.
Click to expand...
Click to collapse
I beleive I flashed twrp origionally from fastboot, that was months ago though when we got the 4.4.4 update.
Do you mean I need to flash that zip from fastboot?
I'm worried about trying to flash firmware with the phone in a strange state. I'm almost thinking that something went bad inside the phone, but not convinced yet. It has been doing strange things lately, constant searching for location, pausing itself durring playback of music, and some random restarts. I haven't been messing it it so it seems strange to all of a sudden have these issues after many months.
Justintoxicated said:
I beleive I flashed twrp origionally from fastboot, that was months ago though when we got the 4.4.4 update.
Do you mean I need to flash that zip from fastboot?
I'm worried about trying to flash firmware with the phone in a strange state. I'm almost thinking that something went bad inside the phone, but not convinced yet. It has been doing strange things lately, constant searching for location, pausing itself durring playback of music, and some random restarts. I haven't been messing it it so it seems strange to all of a sudden have these issues after many months.
Click to expand...
Click to collapse
Nah man. Just reflash the firmware zip that contains twrp and report back. The older twrp are not safe to use on the newer firmware. I have a pda thread stickied in the general section that explains. Phone is likely fine.
dottat said:
Nah man. Just reflash the firmware zip that contains twrp and report back. The older twrp are not safe to use on the newer firmware. I have a pda thread stickied in the general section that explains. Phone is likely fine.
Click to expand...
Click to collapse
Ok, yea, I flashed the new firmware (with twrp) using fastboot , I'm still stuck on the same screen though. I did not install lolipop because I need to get the phone to USB mode to copy it over, which I cannot do because it will not start up.
Justintoxicated said:
Ok, yea, I flashed the new firmware (with twrp) using fastboot , I'm still stuck on the same screen though.
Click to expand...
Click to collapse
Ok...so follow me...if you flashed what you thought was cache on the new firmware but using an older twrp you wiped system instead.
Do you have your stuff backed up?
dottat said:
Ok...so follow me...if you flashed what you thought was cache on the new firmware but using an older twrp you wiped system instead.
Do you have your stuff backed up?
Click to expand...
Click to collapse
I don't know, I made a nandroid to my external memory card and immediately after that I was no longer able to start up... I tried to restore the nandroid and I cannot. So I would say no I am probably not backed up. I do still have RDKN rom on the memory card for 4.4.3, should I try to re-install that?
TWRP is now version 2.8.5.0, so apparently it updated correctly (I think before it was 2.8.1)
Justintoxicated said:
I don't know, I made a nandroid to my external memory card and immediately after that I was no longer able to start up... I tried to restore the nandroid and I cannot. So I would say no I am probably not backed up. I do still have RDKN rom on the memory card for 4.4.3, should I try to re-install that?
Click to expand...
Click to collapse
No. Your best bet to get your stuff back would be to downgrade firmware back to 4.4.4 and reflash the latest twrp img only and then restore your nand.
dottat said:
No. Your best bet to get your stuff back would be to downgrade firmware back to 4.4.4 and reflash the latest twrp img only and then restore your nand.
Click to expand...
Click to collapse
Ok my internet is not working on my laptop at work (only of the PC I'm on and no way to transfer files without my phone), so I guess I will try to do this when I get home. At this point I don't even care about my data, I wanted to save my text conversations but other than that everything I need should be saved in my titanium backup.
Justintoxicated said:
Ok my internet is not working on my laptop at work, so I guess I will try to do this when I get home. At this point I don't even care about my data, I wanted to save my text conversations but other than that everything I need should be saved in my titanium backup.
Click to expand...
Click to collapse
And that's what I figured. So flash 4.4.4. Flash latest twrp. Restore nand from ext sd. Boot up. Install this app.
https://www.androidfilehost.com/?fid=95916177934537937
Run it and link to your Google account and make it perform a backup.
It will do your apps/email accounts/texts/even home screen layout. And it will do it once a day for you automatically or on demand whenever.
Once you get a good backup on this app you can simply flash the new ruu and use this app to restore.
dottat said:
And that's what I figured. So flash 4.4.4. Flash latest twrp. Restore nand from ext sd. Boot up. Install this app.
https://www.androidfilehost.com/?fid=95916177934537937
Run it and link to your Google account and make it perform a backup.
It will do your apps/email accounts/texts/even home screen layout. And it will do it once a day for you automatically or on demand whenever.
Once you get a good backup on this app you can simply flash the new ruu and use this app to restore.
Click to expand...
Click to collapse
Update, restarted the computer and I was able to restore the old firmware. I re-installed the old rom afterwards (not my nandroid) and I am unable to get into the OS. Well technically I get prompted to select a language, after which the phone reboots back to the S-off androids with skateboards bootloader. Does this mean my phone is toast?
Hey guys, should I S-on the phone load the stock bootloader and try to return it? It is over a year old so I think I will need to use my insurance ($100). What is the best way to go about doing this?
Also when I get my replacement phone will there still be a way to S-off?
Thanks,
- Jusitn
The problem appears to be something wrong with my micro SD card! I removed the micro SD card and I can boot up fine. I guess I need to find another way to copy the rom to the micro SD install the rom then remove the micro SD card.
edit:
Oh this is worse than paying $100 for a new phone. It appears that creating a backup instead of creating a backup, actually corrupted my memory card. Now all the photos are backed up to the cloud but it will take me hours and hours to get all my apps back to the way they were. Some Security camera settings, Rifle target hand load development all gone. Audio book place holders, all notes taken etc. Nothing life or death but those security cameras will take me forever to figure out. I know I know, why not create a backup right? Well that's what I was trying to do!
So I was able to get back some data using some recovery software, unfortunately I was not able to retrieve the nandroid or the titanium backup files. Pictures were backed up to the could and music licenses and other hting I can add back on from the PC. Very time consuming though.
Anyways, what should I do now? Should I just reformat the SD card and continue to use it or should I assume that this happened because the card is bad and replace it with something else?
Justintoxicated said:
So I was able to get back some data using some recovery software, unfortunately I was not able to retrieve the nandroid or the titanium backup files. Pictures were backed up to the could and music licenses and other hting I can add back on from the PC. Very time consuming though.
Anyways, what should I do now? Should I just reformat the SD card and continue to use it or should I assume that this happened because the card is bad and replace it with something else?
Click to expand...
Click to collapse
I don't know what file system you're using but assuming it's one that windows can read, connect it to a PC and run chkdsk on it. If you don't know how to do that from a command prompt, right click on the drive in windows explorer and choose properties. Then tools and then click on the check now button under Error-checking. A small window will open. A line that says automatically fix file system errors will be checked by default. In your case, I'd suggest also checking the line that says "scan for and attempt recovery of bad sectors". It'll take a while for it to complete with that line checked so be patient. If you're lucky, it might just fix your problem. No promises but it's worth a try.
When it's done you can look in your event viewer to see what it found, if anything. If it finds bad sectors, I wouldn't trust the card. It can be used but there's no guarantee that more problems won't pop up. Maybe, maybe not.
To get to your event viewer, in Win 7 (not sure about Windows 8) click start and in the search box type event.vwr. I'm not sure what category you have to look under in there but perhaps under Winlogon. That's where you'll find it if it requires a reboot to check the card but that's not likely so I'm not sure.
robocuff said:
I don't know what file system you're using but assuming it's one that windows can read, connect it to a PC and run chkdsk on it. If you don't know how to do that from a command prompt, right click on the drive in windows explorer and choose properties. Then tools and then click on the check now button under Error-checking. A small window will open. A line that says automatically fix file system errors will be checked by default. In your case, I'd suggest also checking the line that says "scan for and attempt recovery of bad sectors". It'll take a while for it to complete with that line checked so be patient. If you're lucky, it might just fix your problem. No promises but it's worth a try.
When it's done you can look in your event viewer to see what it found, if anything. If it finds bad sectors, I wouldn't trust the card. It can be used but there's no guarantee that more problems won't pop up. Maybe, maybe not.
To get to your event viewer, in Win 7 (not sure about Windows 8) click start and in the search box type event.vwr. I'm not sure what category you have to look under in there but perhaps under Winlogon. That's where you'll find it if it requires a reboot to check the card but that's not likely so I'm not sure.
Click to expand...
Click to collapse
exFat for the card, and yes I am on windows 7. I tried to run a check as it was detected as having problems when I plugged the card into my laptop. Then it said I needed to dismount the drive and I said ok. Then it would just hang up. I reformatted the card and then ran the checkdisk again and it tells me that there are no problems now. I guess the card is ok and the issue was caused by TWRP? Not very cool when creating a back delete all your titanium backups and your nandroid that you were trying to create. Unfortunately I have to start from scratch on everything now. I even tried restoring to an older nandroid from May that was saved on my computer but that failed as well. for different reasons.
Justintoxicated said:
exFat for the card, and yes I am on windows 7. I tried to run a check as it was detected as having problems when I plugged the card into my laptop. Then it said I needed to dismount the drive and I said ok. Then it would just hang up. I reformatted the card and then ran the checkdisk again and it tells me that there are no problems now. I guess the card is ok and the issue was caused by TWRP? Not very cool when creating a back delete all your titanium backups and your nandroid that you were trying to create. Unfortunately I have to start from scratch on everything now. I even tried restoring to an older nandroid from May that was saved on my computer but that failed as well. for different reasons.
Click to expand...
Click to collapse
What reason did the restore fail for? And don't ever s-on unless you have let me have a crack at a phone. Not one thing you have said so far makes me think its phone. Unfortunately I have ended up with corrupt exfat discs before too. Sucks.
dottat said:
What reason did the restore fail for? And don't ever s-on unless you have let me have a crack at a phone. Not one thing you have said so far makes me think its phone. Unfortunately I have ended up with corrupt exfat discs before too. Sucks.
Click to expand...
Click to collapse
I don't remember, probably missing a file or something.
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