HI i installed fulmics rom and it did not work , now it will not allow me to install a rom because twrp says "done" almost instantly , how can i delete fulmics. I have 855 international version. THanks
stupify007 said:
HI i installed fulmics rom and it did not work , now it will not allow me to install a rom because twrp says "done" almost instantly , how can i delete fulmics. I have 855 international version. THanks
Click to expand...
Click to collapse
When you boot to TWRP, choose the "Wipe" option, on the next screen, choose "Advanced Wipe", then on the next screen, choose "system" and "data" partitions(do not choose any of the other partitions). Then slide the slider at the bottom to wipe, then tap the home button in TWRP and choose the "Install" option and flash your RIM like you normally would, then after it flashes, wipe cache and Dalvik/ART cache, after it wipes the caches, select reboot and you're done.
Sent from my SCH-I535 using Tapatalk
Didn't Work
hi, that didn't work, it says it has done but then it boots straight back up into fulmics. Any other ideas.
Droidriven said:
When you boot to TWRP, choose the "Wipe" option, on the next screen, choose "Advanced Wipe", then on the next screen, choose "system" and "data" partitions(do not choose any of the other partitions). Then slide the slider at the bottom to wipe, then tap the home button in TWRP and choose the "Install" option and flash your RIM like you normally would, then after it flashes, wipe cache and Dalvik/ART cache, after it wipes the caches, select reboot and you're done.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
hi, that didn't work, it says it has done but then it boots straight back up into fulmics. Any other ideas.
stupify007 said:
hi, that didn't work, it says it has done but then it boots straight back up into fulmics. Any other ideas.
Click to expand...
Click to collapse
There is probably something wrong with your recovery. They flashing an older or newer version of TWRP for your model number, then try flashing a different ROM.
If your recovery was working correctly then the steps to wipe that I told you about should have wiped your system partition, if it had done that properly then you wouldn't have anything to boot to at this point if your new ROM didn't flash. Since you booted to the ROM you tried to wipe then it didn't wipe.
Also, make sure that you still have root before you flash another recovery, use the root checker app, if you don't have root, try flashing SuperSU.zip in TWRP, then try flashing the new ROM.
Droidriven said:
There is probably something wrong with your recovery. They flashing an older or newer version of TWRP for your model number, then try flashing a different ROM.
If your recovery was working correctly then the steps to wipe that I told you about should have wiped your system partition, if it had done that properly then you wouldn't have anything to boot to at this point if your new ROM didn't flash. Since you booted to the ROM you tried to wipe then it didn't wipe.
Also, make sure that you still have root before you flash another recovery, use the root checker app, if you don't have root, try flashing SuperSU.zip in TWRP, then try flashing the new ROM.
Click to expand...
Click to collapse
I never faced this issue before, I had installed roms before and was able to flash a new rom , so could the recovery really be the issue.
stupify007 said:
I never faced this issue before, I had installed roms before and was able to flash a new rom , so could the recovery really be the issue.
Click to expand...
Click to collapse
Just try another recovery and eliminate that possibility, you're not gonna cause any issues with the new recovery unless you use the wrong one.
Sent from my SCH-I535 using Tapatalk
stupify007 said:
I never faced this issue before, I had installed roms before and was able to flash a new rom , so could the recovery really be the issue.
Click to expand...
Click to collapse
Try advanced wipe including everything. then flash stock rom or any official ones. If you got qualcomm device then use QFIL or Qualcomm Flash Tool
hi i just tried that and it didn't do anything, once again it says done but it didn't do anything, I think it may be the recovery as suggested by Droidriven. I am going to try and flash a different version of TWRP or maybe clockworkmod recovery , I will keep you updated. But do you guys have any suggestions to what may have caused this, Fulmics never worked for me.
Droidriven said:
Just try another recovery and eliminate that possibility, you're not gonna cause any issues with the new recovery unless you use the wrong one.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
[[QUOTING MY POST SO YOU CAN SEE]]
.hi i just tried that and it didn't do anything, once again it says done but it didn't do anything, I think it may be the recovery as suggested by Droidriven. I am going to try and flash a different version of TWRP or maybe clockworkmod recovery , I will keep you updated. But do you guys have any suggestions to what may have caused this, Fulmics never worked for me.
Also guys , i installed TWRP using my OS and now it doesnt work so what is the alternative, I have all pc drivers?
stupify007 said:
Also guys , i installed TWRP using my OS and now it doesnt work so what is the alternative, I have all pc drivers?
Click to expand...
Click to collapse
It sounds to me like you flashed something that was not made for your model number. Find the correct stock firmware and flash that, then start over and find something different for your device this time.
Sent from my SCH-I535 using Tapatalk
quick story. I reinstalled of the same version (2.8) and the problem is still here, I am going to try to install a different version.
Sorry to keep posting but I tried a factory reset using TWRP and it says failed. Could that mean something.
Actually guys, IT says failed underneath for everything but in the console it shows no signs of failure.
SOrry guys for being a noob, this can now be shut down as i have fixed the problem by unchecking simulate actions.
stupify007 said:
SOrry guys for being a noob, this can now be shut down as i have fixed the problem by unchecking simulate actions.
Click to expand...
Click to collapse
How in the world did that setting get changed, it should have been set to what you needed by default.
Sent from my SCH-I535 using Tapatalk
Related
hi all,
Ok, I'm new to this stuff.
1. used the simple root and it worked great.
2. I then flashed CM7 and it worked great except market was not on it.
3. I downloaded and flashed gapps-hdpi-20101114-signed.zip by mistake, not realizing I had to use another gapps.
4. After I flashed it, the cm7 and android setup screens kept cycling between each other.
5. I restored to clockworkmod (sp) and then deleted the gapps and tried to then flash cm7. It didn't cycle between cm7 and android setup, but the cm7 screens kept cycling and never got past that.
6. I thought perhaps it was just cm7 now, so I tried miui and it's doing the same thing. It's cycling between the gingerbread man and MIUI with the status bar and won't do anything else.
Very frustrated. what have I done and how do I fix it?
Thanks folks,
Brett
I believe that those ROMs both require ENG S-OFF. Open simple root on your computer, click Fixes, then apply the fix there. Also, did you make sure you cleared your Dalvik cache before flashing? Always do a factory reset AND clear dalvik cache when changing ROMs.
make sure you have wifi off in your first boot
ardynine said:
make sure you have wifi off in your first boot
Click to expand...
Click to collapse
From reading the first post, he got in, rebooted to flash gapps and ended up in bootloop afterwards
EtherealRemnant said:
From reading the first post, he got in, rebooted to flash gapps and ended up in bootloop afterwards
Click to expand...
Click to collapse
Thanks ER. I'll try your method this evening.
I'll report back.
thanks!
brett
EtherealRemnant said:
I believe that those ROMs both require ENG S-OFF.
Click to expand...
Click to collapse
I can say with no doubt whatsoever, no.
id10terrordfw said:
I can say with no doubt whatsoever, no.
Click to expand...
Click to collapse
any suggestions then???????
I tried doing the ENG-off and still the same hang up on the front screen.
Any help please?
thanks,
brett
what method do you use to flash cm7? what exactly do you do.
to clarify what is your exact process for flashing the rom?
mudknot2005 said:
what method do you use to flash cm7? what exactly do you do.
Click to expand...
Click to collapse
Hi. Thanks.
I use rom manager to boot to recovery. Then I install zip from sd card. I go through the process until it says reboot. It's when I reboot that I get stuck in the bootloop. It just cycles from the CM7 circular arrow to blank and then to the arrow thing again. MIUI does the same between the gingerbread guy and the status bar and back.
I then take the battery out, take out the sdcard, down volume & power, reinsert sdcard and do a restore so I can use my phone again in clockworkmod 3.0.0.6.
thanks,
brett
sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..
mudknot2005 said:
sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..
Click to expand...
Click to collapse
actually, I did that.
it's weird. I restored a few times, did the above you suggested, and still in a loop. The first time I installed CM7 it was great, then the gapps thing seems to have screwed it up.
I'm lost.
brett
bdws1975 said:
actually, I did that.
it's weird. I restored a few times, did the above you suggested, and still in a loop. The first time I installed CM7 it was great, then the gapps thing seems to have screwed it up.
I'm lost.
brett
Click to expand...
Click to collapse
Probably a silly question but you're doing full reinstalls, right? Not using a nandroid backup? I can't think of any reason that you should be boot looping permanently from flashing the gapps if you're going into clockwork, doing a factory reset, wiping the cache, then wiping the Dalvik cache, then flashing the ROM.
EtherealRemnant said:
Probably a silly question but you're doing full reinstalls, right? Not using a nandroid backup? I can't think of any reason that you should be boot looping permanently from flashing the gapps if you're going into clockwork, doing a factory reset, wiping the cache, then wiping the Dalvik cache, then flashing the ROM.
Click to expand...
Click to collapse
hmm. I'm a little new to this, but I'm using the backup/restore option in recovery mode and am then flashing one of the backups. Could that be the problem?
If it is, how do I do a full reinstall?
thanks again for your help,
brett
mudknot2005 said:
sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..
Click to expand...
Click to collapse
Without a full wipe I thought it would just bootloop?
Do a full wipe then reinstall cm7 and gapps.
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
bdws1975 said:
hmm. I'm a little new to this, but I'm using the backup/restore option in recovery mode and am then flashing one of the backups. Could that be the problem?
If it is, how do I do a full reinstall?
thanks again for your help,
brett
Click to expand...
Click to collapse
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.
EtherealRemnant said:
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.
Click to expand...
Click to collapse
I'll give it a shot and then get back to you.
I do believe, however, that the restore I'm doing is the backup I did right before I did the original cm7 flash. I'll try.
thanks!
If you toggle wifi on after the first boot it goes into a bootloop. This is a know bug not a hunch.
EtherealRemnant said:
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.
Click to expand...
Click to collapse
DUDE!!!! You freaking rock. I got it!
I installed MIUI and it's amazing. Thank you very much.
Brett
Mustang302LX said:
Without a full wipe I thought it would just bootloop?
Do a full wipe then reinstall cm7 and gapps.
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
Click to expand...
Click to collapse
thank you!!!!! I really appreciate your help!
So I'm trying to install custom ROM on my friend Nexus 5, should be a 2 minute job turns into 2 hours..
CWM is giving me a list of can't mount anything basically.
I tried fe-flashing the entire phone back to stock via fastboot, that went fine, flashed recovery again to CWM.. and can't mount anything again..
I need to be able to mount in order to install zip...
anybody can help??
now i got it to boot with purity ROM, telling me on startup with no google sign in... "
System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
THE_KINGDOM said:
now i got it to boot with purity ROM, telling me on startup with no google sign in... "
System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Click to expand...
Click to collapse
yup, you will need to wipe and reflash.
still can't mount sdcard in recovery..
so i can't do anything.. I had to sideload the ROM..
so i've done a bat flash all, restore to stock..
I don't get why everytime i flash CWM custom recovery I can't load anything.. how the hell do I install purity from stock if I can't install CWM ?!
THE_KINGDOM said:
so i've done a bat flash all, restore to stock..
I don't get why everytime i flash CWM custom recovery I can't load anything.. how the hell do I install purity from stock if I can't install CWM ?!
Click to expand...
Click to collapse
try twrp recovery
but i've been using CWM forever on every nexus device without problems..
I though process is simple.
1. Unlock bootloader
2. Fastboot flash recovery recovery.img (cwm)
3. wipe & install custom ROM (Purity)
4. gapps
5. start phone..
what am I missing???
so I tried installing the previous version of CWM 6.0.4.4 and CWM problems seems to be resolved.. clearly they must have issued with the latest version.
Now im able to read /sdcard and hopfully install purity ROM, gapps etc.
but I'm still getting the system UID's inconsistent issue...
what a colossal waste of time...
ok phone back to stock at again with a batch restore all file.. factory files...
how the ****ing hell do I install a custom ROM?!?!?!? Like iv'e done this a million times before.. what am I missing??????
anybody?????
THE_KINGDOM said:
ok phone back to stock at again with a batch restore all file.. factory files...
how the ****ing hell do I install a custom ROM?!?!?!? Like iv'e done this a million times before.. what am I missing??????
Click to expand...
Click to collapse
Put a custom ROM.zip and gapps package on storage, flash in recovery, flash SuperSU if necessary?
THE_KINGDOM said:
anybody?????
Click to expand...
Click to collapse
No bumping within 24 hours is the forum rule. I also believe they should set a punctuation limit. Chill out
Sent from my Nexus 5 using Tapatalk
Lethargy said:
Put a custom ROM.zip and gapps package on storage, flash in recovery, flash SuperSU if necessary?
Click to expand...
Click to collapse
this is what ive been doing.. when phone boots it doesn't ask for google login credentials and goes straight to android is upgrading as if I did a dirty flash and then tell me i have a UID mismatch, and to wipe data partition..
i've now reinstalled this phone close to 6 times.. I cannot figure this out
THE_KINGDOM said:
what am I missing??????
Click to expand...
Click to collapse
cwm recovery SUCKS. but if you are unwilling to try other recoveries, oh well..
THE_KINGDOM said:
this is what ive been doing.. when phone boots it doesn't ask for google login credentials and goes straight to android is upgrading as if I did a dirty flash and then tell me i have a UID mismatch, and to wipe data partition..
i've now reinstalled this phone close to 6 times.. I cannot figure this out
Click to expand...
Click to collapse
Well somewhere you're not wiping properly. Flash the factory images again using the flash-all.bat included in the compressed file as it'll wipe everything, then go from there.
Stock CWM always has issues. It's based on an outdated version of Android so it doesn't always play well with KitKat. I would recommend either TWRP or Philz Touch CWM.
Lethargy said:
Well somewhere you're not wiping properly. Flash the factory images again using the flash-all.bat included in the compressed file as it'll wipe everything, then go from there.
Click to expand...
Click to collapse
flashed factory img aroudn 6 times now.. every single time i got back to put on CWM and then flash the rom i get a UID mismatch, bunch of force closes etc..
BirchBarlow said:
Stock CWM always has issues. It's based on an outdated version of Android so it doesn't always play well with KitKat. I would recommend either TWRP or Philz Touch CWM.
Click to expand...
Click to collapse
CWM is built from CM11 4.4.3 source code.. But yeah it has issues., lacks functionality and also is antiquated
Sent from my Nexus 5 using Tapatalk
THE_KINGDOM said:
flashed factory img aroudn 6 times now.. every single time i got back to put on CWM and then flash the rom i get a UID mismatch, bunch of force closes etc..
Click to expand...
Click to collapse
Don't know what to tell you, just try TWRP. I've had issues with CWM on every single device I've put a custom ROM onto (Xperia Arc S, HTC One M7, Galaxy S4, HTC One M8, Galaxy Note 3, Xperia Z, Nexus 5), and never had a single issue with TWRP on any.
gonna try Philz Touch CWM and if that doesn't work then TWRP
Hey there!
I'm hoping that someone can help me out. My nephew who's a wanna-be geek was going to update my ROM (which didn't to be done really, but he wanted to show me what he was able to do). He went and downloaded the latest CM 11, rebooted and went into TWRP 2.7.0.1, did a factory reset, an advanced wipe, and did the Format Data. When he did that, it got stuck in a loop. Nothing happened. He tried to install the ROM he downloaded, and NOTHING! Long story short, by him doing the Format Data, he wiped out my partitions. TWRP, no matter what I try to do tells me it's unable to mount 'data' or 'media' etc. etc. Which is leading me to believe I have no partitions left. I've tried installing the latest update from Asus, and no dice. I've tried restoring backups that I have on my micro SD, and that's not working.
Can someone please help me and tell me how to fix this? Can I get my partitions back? I'm really hoping that I don't have to send this tablet off to Asus in Dallas, TX to have it repaired.
I'm using a loaner tablet from a rental store, hoping I can get my TF 300 fixed.
Any help is deeply and sincerely appreciated.
Omega
Sent from my SM-P600 using Tapatalk
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Duchman said:
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Click to expand...
Click to collapse
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Omega Recon said:
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
You could try flashing a newer recovery first, I think 2.7.1.0 is available for your device. Also try doing a hard reset by cold booting - here's a how-to: https://www.youtube.com/watch?v=oTU38Ewh8qo (wipe the cache afterwards)
If that doesn't help, reverting to stock is probably your best option. Try this: http://forum.xda-developers.com/showthread.php?t=1757077 (be sure to grab the correct firmware and back up your files)
Have you tried installing any other custom ROM? Does it give you the same error when you try to restore your backup?
Here's what I've come across so far. I did the reset, and that did nothing.
Tried to flash the stock version, after a few seconds, TWRP popped up with FAILED.
I've tried flashing Omni ROM. It will flash, load up, and gets stuck at the boot screen or boot animation. This happens with just about every ROM I try to flash.
Been looking for TWRP 2.7.1.0. I'm not seeing it listed on TWRPs site. Where can I get a copy? Thanks!
Sent from my SM-P600 using Tapatalk
Here you go: http://forum.xda-developers.com/showthread.php?t=2772093
Also do try flashing another recovery, PhilZ for instance: http://forum.xda-developers.com/showthread.php?t=2597860
Did you try wiping all of the partitions again?
Hi! I just installed a new Custom ROM for my phone. After 5 minutes I wanted to create a backup. So I started ROM Manager. I entered the name, and hit OK. The phone booted into a crashed recovery mode. So I took the battery out and rebooted the phone. It didn't boot into my Custom ROM. It booted into recovery. So I am stuck inside the recovery mode and can't boot normally.
Phone: Samsung Galaxy Mini (GT-S5570)
Recovery: CWM Recovery
Custom ROM: CyanogenMod
Hello,
If you can boot into the recovery, do a factory reset and flash back the custom rom. And then reboot the device, once you rebooted the device will boot into system. And then you're done!
Good luck!
HashyCode. :good:
It still puts me into recovery
HashyCode said:
Hello,
If you can boot into the recovery, do a factory reset and flash back the custom rom. And then reboot the device, once you rebooted the device will boot into system. And then you're done!
Good luck!
HashyCode. :good:
Click to expand...
Click to collapse
I tried it. I wiped /system, /data, /cache and I did a factory reset. Flashed it back but it still puts me into recovery.
xdcsaba said:
I tried it. I wiped /system, /data, /cache and I did a factory reset. Flashed it back but it still puts me into recovery.
Click to expand...
Click to collapse
Flash the original firmware back. And try from the start
HashyCode
It still doesn't work
HashyCode said:
Flash the original firmware back. And try from the start
HashyCode
Click to expand...
Click to collapse
Tried it. Does not work.
xdcsaba said:
Tried it. Does not work.
Click to expand...
Click to collapse
Visit here and try one of them
HashyCode.
Hi, i would like help you with this problem as I myself have experienced it. The things that you should have done are:
1. Always make the backup early on before installing the Custom ROM.
2. When installing a Custom ROM, make sure you have not replaced core system apps
3. Make sure your there are complete symlinks in your ROM otherwise it be hard bricked. Ouch.
4. Before installing a Custom ROM, make sure they are from experts, like CyanogenMOD, and sure your device is supported for updates.
5.[Most Important] The only things to wipe when installing a ROM are : 1. Cache 2. Dalvik Cache 3. User Data, never ever ever ever WIPE your system folder with root access on it. This will always ensure that you will reboot into recovery, and it will be annoying to root your device w/o ADB USB Debugging on.
6. Make sure that there are no system apps missing on your Custom ROM, check for the legibility of the Custom apps installed. Are they pirated perhaps?
7.[Very Important]Always watch a video tutorial for it's errors, and search how to Unbrick your device first before proceeding with an installation.
So that if any problem arises, you will be sure to restore it to it's Stock experience.
8.[Absolutely Important]Make sure that your software counterparts on the PC are compatible and functioning well first before you proceed.
Now tell, me which of the following did you not do?
And if this really helped you a lot, please like. For the sake of those who did their research.
HashyCode said:
Hello,
If you can boot into the recovery, do a factory reset and flash back the custom rom. And then reboot the device, once you rebooted the device will boot into system. And then you're done!
Good luck!
HashyCode. :good:
Click to expand...
Click to collapse
ive already done factory reset like 5 times i still am not able to flash it to custom rom stock condition im going to try using a laptop with windows 7 to see if i can do that way because its not working on the latest windows 8
Kinnngzzzz
Try fastboot?
Hi,
No one seems to have suggested using a program called fastboot. It involves just installing some essential software on a PC, then running the program "Fastboot" along with the desired options.
I strongly suggest trying this: http://forum.xda-developers.com/showthread.php?t=2277112
I am always flashing ROMs and then trying to tweak them and end up messing up the bootloaders, or somehow breaking the system. And then i try using CWM or TWRP and still there remain issues. However, fastboot has always done the job for me.
Hope this helps.
Someone help me with my problem please ??
Use Fastboot!!!
kinnngzzzz said:
Someone help me with my problem please ??
Click to expand...
Click to collapse
kinnngzzzz, you too should use Fastboot! See my post right before yours...
So again, see this link: http://forum.xda-developers.com/showthread.php?t=2277112
I say if fastboot can't get it fixed, nothing will. :victory:
kinnngzzzz said:
Someone help me with my problem please ??
Click to expand...
Click to collapse
As you said that you're going to try with windows 7. Did you tried it? And please! Visit the link which youniqueg33k provided.
HashyCode.
unlocked note 3 n900 t mobile version, has twrp on it but my son either wiped or factory reset it, no operating system on it, d/l one (zip file) clicked install selected the zip, but it just seems to sit on the samsung galaxy note 3 screen, how long should this take? While I can do some stuff on computers, phones are a different fish.
kevin24018 said:
unlocked note 3 n900 t mobile version, has twrp on it but my son either wiped or factory reset it, no operating system on it, d/l one (zip file) clicked install selected the zip, but it just seems to sit on the samsung galaxy note 3 screen, how long should this take? While I can do some stuff on computers, phones are a different fish.
Click to expand...
Click to collapse
You booted to recovery, selected install zip, then after flashing, did you factory reset, wipe cache and wipe dalvik cache? If you didn't do the factory reset and wipe the 2 cache partitions, that would explain the bootloop(stuck at note 3 screen). If this is what you did, try booting to TWRP then factory reset and wipe the 2 cache partitions then reboot, it might take up 20 mins to an hour to restart and load the OS, just give it time to be sure.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You booted to recovery, selected install zip, then after flashing, did you factory reset, wipe cache and wipe dalvik cache? If you didn't do the factory reset and wipe the 2 cache partitions, that would explain the bootloop(stuck at note 3 screen). If this is what you did, try booting to TWRP then factory reset and wipe the 2 cache partitions then reboot, it might take up 20 mins to an hour to restart and load the OS, just give it time to be sure.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I did not do those things, thank you for taking the time to reply. What I did instead was download Odin, found a stock rom and loaded that, it worked the phone is functional. It's kind of fun actually, since I don't actually need this phone. My next step is to find out how to remove the rom and use a different one. I'm guess once it's unlocked it's unlocked and I don't have to contact the company again, right? thanks for your time.
kevin24018 said:
I did not do those things, thank you for taking the time to reply. What I did instead was download Odin, found a stock rom and loaded that, it worked the phone is functional. It's kind of fun actually, since I don't actually need this phone. My next step is to find out how to remove the rom and use a different one. I'm guess once it's unlocked it's unlocked and I don't have to contact the company again, right? thanks for your time.
Click to expand...
Click to collapse
If the stock firmware that you flashed has a locked bootloader, you won't be able to use TWRP or flash custom ROMs. If the bootloader is unlocked, then you can use TWRP and custom ROMs.
If there are any custom ROMs for your specific model number, you can do what you did previously, just do things in the right order this time.
Flash TWRP via Odin, boot into TWRP, select install, then select your custom ROM zip, then select "add more zips", then select the Gapps file to be flashed with your ROM(the correct gapps should be linked in the ROM thread where you find your ROM), swipe the slider to flash. After the ROM and Gapps are flashed, make sure you factory reset, wipe cache and wipe dalvik cache(do not do any other wipes), then reboot and wait for the OS to load and then sign in to the phone. You "should" be good to go after that, then you can install whatever apps you want and set everything up the way you want.
Sent from my LGL84VL using Tapatalk
Droidriven said:
If the stock firmware that you flashed has a locked bootloader, you won't be able to use TWRP or flash custom ROMs. If the bootloader is unlocked, then you can use TWRP and custom ROMs.
If there are any custom ROMs for your specific model number, you can do what you did previously, just do things in the right order this time.
Flash TWRP via Odin, boot into TWRP, select install, then select your custom ROM zip, then select "add more zips", then select the Gapps file to be flashed with your ROM(the correct gapps should be linked in the ROM thread where you find your ROM), swipe the slider to flash. After the ROM and Gapps are flashed, make sure you factory reset, wipe cache and wipe dalvik cache(do not do any other wipes), then reboot and wait for the OS to load and then sign in to the phone. You "should" be good to go after that, then you can install whatever apps you want and set everything up the way you want.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
yeah I think I may have relocked it I'll mess with it later, but I think I tried to load it back into twrp with the power,home and up vol button but it didn't load into twrp, would I have to call tmobile to have it unlocked again? thanks for the help btw, much appreciated.
kevin24018 said:
yeah I think I may have relocked it I'll mess with it later, but I think I tried to load it back into twrp with the power,home and up vol button but it didn't load into twrp, would I have to call tmobile to have it unlocked again? thanks for the help btw, much appreciated.
Click to expand...
Click to collapse
TWRP was removed and replaced with stock recovery when you flashed the firmware via Odin.
Most Samsung devices with locked bootloader these days, can't be unlocked. You might get lucky though, T-mobile might unlock it for you or allow you to unlock it. If you get it unlocked, you can flash it with custom software, but if they won't allow it to be unlocked, you'll be out of luck and stuck with stock.
Sent from my LGL84VL using Tapatalk
Droidriven said:
TWRP was removed and replaced with stock recovery when you flashed the firmware via Odin.
Most Samsung devices with locked bootloader these days, can't be unlocked. You might get lucky though, T-mobile might unlock it for you or allow you to unlock it. If you get it unlocked, you can flash it with custom software, but if they won't allow it to be unlocked, you'll be out of luck and stuck with stock.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
bummer, well I'll give it a try, I couldn't get anything to load with twrp so i used Odin, still learning this stuff, thanks again.