I have a problem with my Galaxy S 3
When i bought it out the box i was able to root easily and install custom rom (Wicked) with no problems but then i had to restore back to stock using ODIN returning back to stock and running everything stock i also reset the counter beause i wanted to exchange the phone turn out i cannot
so i re-rooted the phone the same way and tried to install the custom rom it gave me status 7 error he only thing that worked is my Backups
so i returned back to stock again and re-root this time i didnt have the error i just get stuck at the boot logo
i have no idea what to do now. its very frustrating.
ChronoXzX said:
I have a problem with my Galaxy S 3
When i bought it out the box i was able to root easily and install custom rom (Wicked) with no problems but then i had to restore back to stock using ODIN returning back to stock and running everything stock i also reset the counter beause i wanted to exchange the phone turn out i cannot
so i re-rooted the phone the same way and tried to install the custom rom it gave me status 7 error he only thing that worked is my Backups
so i returned back to stock again and re-root this time i didnt have the error i just get stuck at the boot logo
i have no idea what to do now. its very frustrating.
Click to expand...
Click to collapse
same problem i had before. Bothered me for a few days.
1. download rooted stock ROM
2. download goo manager
3. user twpr to flash wicked ROM
hope this will help
Had that problem after Odin reboot into stock recovery and erase and reset, had to do it 2 days ago
Sent from my SGH-T999 using xda app-developers app
theory611 said:
same problem i had before. Bothered me for a few days.
1. download rooted stock ROM
2. download goo manager
3. user twpr to flash wicked ROM
hope this will help
Click to expand...
Click to collapse
Can you link me the rooted stock rom that you used
Plz ive tried everything its real annoying that my phone wont boot the custom rom
Its installed successfully but nothing after the reboot just the logo screen of the custom rom
Did you wipe the cache/dalvik?
psykhotic said:
Did you wipe the cache/dalvik?
Click to expand...
Click to collapse
Yeah I did
I do factory setting then I wipe cache then I do the dalvik cache
Then I finally install I do it everytime it doesnt work. Is it because maybe I unroot the phone wrong??? Is that even possible?? Lol
Try This:
http://forum.xda-developers.com/attachment.php?attachmentid=1404381&d=1350325570
Flash this TWRP Recovery Through ODIN, and try to reinstall the ROM
DroidDonX said:
Try This:
http://forum.xda-developers.com/attachment.php?attachmentid=1404381&d=1350325570
Flash this TWRP Recovery Through ODIN, and try to reinstall the ROM
Click to expand...
Click to collapse
ill try that when i get home
but note so far no rom has been working i can successfully install it with no errors
but when it wants to boot nothing happens just stuck at the Logo screen :/
i think its because i unroot using odin the wrong way or something idk but ever since i un rooted the device this started to happen..
I think status 7 error is a md5 mismatch. Redownload the rom you want. Also some people have had issues downloading to the phone so use a pc and transfer it.
jcbofkc said:
I think status 7 error is a md5 mismatch. Redownload the rom you want. Also some people have had issues downloading to the phone so use a pc and transfer it.
Click to expand...
Click to collapse
Ok ill do that but what if I dont get the error the rom finishes installing and the aroma installer says status 0 I do not know what it means
There are a couple possibilites here.
1) Your recovery is outdated. Update it. CWM will work just as well as TWRP. A lot of people have been advertising TWRP like they are being paid to do so. Either will work fine, but it must be updated to the latest version. The "CWM makes you lose IMEI" slander is starting to get old as well. There have been several documented cases on this forum where people have lost IMEI using TWRP. That's of course assuming the custom recoveries are actually causing it. We don't even know that. In any case, a reboot nvbackup would prevent all of this nonsense. I can't believe people still aren't doing this.
2) You are attempting to flash roms that are not for your device. Please give us a forum link to the rom you are attempting to flash.
Aerowinder said:
There are a couple possibilites here.
1) Your recovery is outdated. Update it. CWM will work just as well as TWRP. A lot of people have been advertising TWRP like they are being paid to do so. Either will work fine, but it must be updated to the latest version. The "CWM makes you lose IMEI" slander is starting to get old as well. There have been several documented cases on this forum where people have lost IMEI using TWRP. That's of course assuming the custom recoveries are actually causing it. We don't even know that. In any case, a reboot nvbackup would prevent all of this nonsense. I can't believe people still aren't doing this.
2) You are attempting to flash roms that are not for your device. Please give us a forum link to the rom you are attempting to flash.
Click to expand...
Click to collapse
I would gladly take this slightly off course and ask you to find me one with the issue, as I've read lots and lots about the issue, it is and has been a CWM issue. Here are the Docs Spreadsheet
https://docs.google.com/spreadsheet/ccc?key=0Arzp20hXNPi4dFg3UUozS2FQaERYNVJRVm1hWmJYQ3c#gid=0
and here is the huge thread about the issue
http://forum.xda-developers.com/showthread.php?t=1794657&highlight=imei
Aerowinder said:
There are a couple possibilites here.
1) Your recovery is outdated. Update it. CWM will work just as well as TWRP. A lot of people have been advertising TWRP like they are being paid to do so. Either will work fine, but it must be updated to the latest version. The "CWM makes you lose IMEI" slander is starting to get old as well. There have been several documented cases on this forum where people have lost IMEI using TWRP. That's of course assuming the custom recoveries are actually causing it. We don't even know that. In any case, a reboot nvbackup would prevent all of this nonsense. I can't believe people still aren't doing this.
2) You are attempting to flash roms that are not for your device. Please give us a forum link to the rom you are attempting to flash.
Click to expand...
Click to collapse
I have the latest CMW recovery touch
tried it with both of the recoveries same deal :/
and the ROm im trying to flash is
http://forum.xda-developers.com/showthread.php?t=1804260
ANd noob question what happens when i lose my Imei?? does it brick or prevent installation?
ANd noob question what happens when i lose my Imei?? does it brick or prevent installation?
Click to expand...
Click to collapse
Might as well be a brick. Just back it up the way I said and you don't need to worry about it.
mt3g said:
I would gladly take this slightly off course and ask you to find me one with the issue, as I've read lots and lots about the issue, it is and has been a CWM issue. Here are the Docs Spreadsheet
https://docs.google.com/spreadsheet/ccc?key=0Arzp20hXNPi4dFg3UUozS2FQaERYNVJRVm1hWmJYQ3c#gid=0
Click to expand...
Click to collapse
This spreadsheet doesn't prove anything. I see 18 CWM IMEI losses. 3 of which are on CWM v6. Out of 116 users reporting. The vast majority of reporting users are using CWM with success. This is hardly evidence. If anything, it implies CWM is more popular than TWRP. But, there is no proof of that in the spreadsheet, either. You would need thousands of reporting users to establish any kind of usable baseline. Last I checked, no one is sure why the IMEI loss happens or what, exactly, causes it. People do have their suspicions (or superstitions), though. I've flashed hundreds of files with CWM, and never had a single issue. And so have thousands of other XDA forum members.
and here is the huge thread about the issue
http://forum.xda-developers.com/showthread.php?t=1794657&highlight=imei
Click to expand...
Click to collapse
What about it? I think I posted a backup script there a couple months ago.
Aerowinder said:
Might as well be a brick. Just back it up the way I said and you don't need to worry about it.
This spreadsheet doesn't prove anything. I see 18 CWM IMEI losses. 3 of which are on CWM v6. Out of 116 users reporting. The vast majority of reporting users are using CWM with success. This is hardly evidence. If anything, it implies CWM is more popular than TWRP. But, there is no proof of that in the spreadsheet, either. You would need thousands of reporting users to establish any kind of usable baseline. Last I checked, no one is sure why the IMEI loss happens or what, exactly, causes it. People do have their suspicions (or superstitions), though. I've flashed hundreds of files with CWM, and never had a single issue. And so have thousands of other XDA forum members.
What about it? I think I posted a backup script there a couple months ago.
Click to expand...
Click to collapse
But no one lossed it using TWRP, that's my only point. With out a doubt CWM is more popular, think of it this way. More people are going to respond and or look for a thread regarding the issue compared to those (TWRP) users who never had the issue, I've been on CWM for a couple weeks try to lose my IMEI and haven't done so yet. Either way I'm not defending either but trying to help people out.
Sent from my SGH-T999 using xda premium
When installing a Rom it just flashes through is that normal?
doesnt it usually take like 2 or 3 minutes to flash a rom that big?
because almost everyone rom i try
Darthstalker
furioustock
wicked
aeonflux
when i format everything using this guide
http://forum.xda-developers.com/showthread.php?t=1946701
The installation for the rom just takes 1 to 2 seconds i that normal?
since i used to have a samsung nexus s it usually takes about 1 - 2 minutes to flash a rom that is greater than 100mb
i just wanted to know maybe that can spark any conclusions.
i am still failing to install a rom and seeing it boot up pass the boot screen.. i really need help please :/
the recovery does not give me any errors at all its installed " successfully "
It should take at least 20 to 45 seconds.
Sent from my SGH-T999 using xda premium
mt3g said:
It should take at least 20 to 45 seconds.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
My phone takes 2 seconds to flssh it says starting flash please wait then it says complete about 2 seconds later
ChronoXzX said:
My phone takes 2 seconds to flssh it says starting flash please wait then it says complete about 2 seconds later
Click to expand...
Click to collapse
which is why it isn't working, how large are the files, what are download steps you are taking? Which recovery... You might have a borked recovery... Try reinstalling the recovery if all else seems normal.
mt3g said:
which is why it isn't working, how large are the files, what are download steps you are taking? Which recovery... You might have a borked recovery... Try reinstalling the recovery if all else seems normal.
Click to expand...
Click to collapse
the files that im trying to install into my phone are about 600mb +
the wiked rom is about 809mb
the darthstalker rom is about 776mb
im using internet download manager to download the roms
ive reinstalled the recovery via the apps ( rom manager and goomanager )
nothing seems to work :/
Related
I've owned a Galaxy S II before, and had it rooted. I followed all the steps, did the odin CWM push, flashed su in recovery, phone has su on it, but locks up when requesting root permission. Use su fix, and it says not rooted. In recovery if I go to one of my older back ups from my old s II, it flashes 1 of them, it boots, but it's a very old version, not ICS which I want. I try to flash a new rom, and within seconds it says it's completed. I've tried MIUI, and CM10 stable version. They get to the boot screen, but goes no further. I let both of them sit for over 10 minutes, each time I would go back into recovery factory wipe, and davlik wipe multiple times to make sure the wipe went through, fix permissions, but still won't boot. I've tried to odin CWM again, and reflash su, and it always says it works, but I still don't have root. Any advise? I basically just want to get a good stable version of CM10. If anybody has a way to upload me a restore point I can flash, I'd be much appreciative of that. I don't know a whole lot to the rooting scene, but I've done it quite a few times, so I'm pretty sure I didn't screw up. The phone works fine, I just noticed after using su fix, my battery drains a lot faster now on stock rom, and that's only with wifi enabled, and bluetooth. I'll lose over 50% in less then 2 1/2 hours with maybe 20 min. of heavy use. I'm sorry if someone already posted this same issue, but I've been searching and searching and can't find a solution. Thank you for any help, or taking the time to read the post, I love XDA, it's the best forum, and you guys are amazing.
My past experiences with odin are terrible. Had to go through 4 phones because Odin ****ed em up. Carrier was mad, but oh well, imo just use another method if possible
nashy10 said:
My past experiences with odin are terrible. Had to go through 4 phones because Odin ****ed em up. Carrier was mad, but oh well, imo just use another method if possible
Click to expand...
Click to collapse
Never had problems with Odin, but when I restore to a backup that was rooted, it's still rooted. Tried to install ROM that way also, bit still hangs on boot screen.
Dagouk said:
Never had problems with Odin, but when I restore to a backup that was rooted, it's still rooted. Tried to install ROM that way also, bit still hangs on boot screen.
Click to expand...
Click to collapse
Clean flash again, if it hangs again, go back to recovery, clear cache, reboot, might help
Fix permissions maybe?
Try a different version of CWM.
There were several versions of SuperSU. Some of them were not working on Hercules. Make sure that you are using the files from this post http://forum.xda-developers.com/showthread.php?t=1311194 (md5sum to check that you do not have an incomplete download).
drakulina said:
Fix permissions maybe?
Try a different version of CWM.
There were several versions of SuperSU. Some of them were not working on Hercules. Make sure that you are using the files from this post http://forum.xda-developers.com/showthread.php?t=1311194 (md5sum to check that you do not have an incomplete download).
Click to expand...
Click to collapse
The links are dead links, I've already tried that post. I used the original cwm I users with my first have, just a different su.
Make sure you dont need an updated binary for su....sometimes it will install and if not up to date will not allow su permission. Open the su app and check if it needs updated.
Sent from my SGH-T989 using xda premium
sinfulgray said:
Make sure you dont need an updated binary for su....sometimes it will install and if not up to date will not allow su permission. Open the su app and check if it needs updated.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Did the play store su update already. Other then that don't see a way to update the binaries.
A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.
jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
I initially flashed all the way back to the TWRP build before 2.3.1 but stopped there. I'll report back with results of your recommendation in the morning!
prboy1969 said:
You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.
Click to expand...
Click to collapse
ROM Manager was something I tried as a last resort as well, it flashed the custom recovery alright, but soft bricked it with a redundant recovery bootloop. I got past that by Odin-ing back to stock.
Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?
prboy1969 said:
Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?
Click to expand...
Click to collapse
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!
n3td3v said:
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!
Click to expand...
Click to collapse
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.
prboy1969 said:
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.
Click to expand...
Click to collapse
I tried formatting the sdcard as well as without the sdcard and even with a different one to no avail. I'm still on the hunt for pda, csc, etc. Odin files. My last resort will be to figure out how to get it replaced at Sprint as a defective device lol
Sent from my SPH-L710 using xda premium
Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium
billard412 said:
Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Yes, stock recovery allows clearing of cache, depending on whose stock recovery I flash. If I flash the toolkit version of stock, I can clear no problems. There are a couple of other stock recoveries, such as this one, in which everything fails as well.
FYI, I have even flashed the stock builds you have on sxtp with the same results.
Thanks for this -- you solved my problem...at least mostly.
I tried to root a new Sprint SG3 by ODIN'ing CWM and then flashing a root.zip file. That epic failed just like your situation where nothing would mount in recovery whether I used CWM or TWRP. I am assuming that something must've changed on the Sprint S3's and that root method must not work anymore (for whatever reason). So I decided to go back to stock recovery and just wait and see if anything further is discovered about this here (I'm not a dev, so I have to wait for other more talented people to solve my problems). However, the stock recovery image that I downloaded from the same "Easy Root" tutorial here didn't work and I still couldn't mount anything.
Saw your post where you stated that the Toolkit stock recovery image worked, so I just tried that and score! However...my poor little recovery android is on his back with a red triangle and a "!". Everything mounts, I can wipe cache, browse around for an update, etc., but I'm a little concerned that my little Android is sick. Should I be? Is that because I have a flash count of 5 so it thinks I have a custom ROM?
Sorry to hijack your thread a little, but my problems seems to be related.
n3td3v said:
A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!
Click to expand...
Click to collapse
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.
swiggs98 said:
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.
Click to expand...
Click to collapse
Same boat. Rooted probably 6 S3 before now and my wife's new S3 I am seeing same thing.
Sent from my SPH-L900 using xda app-developers app
I'm having the same issue. I finally downloaded an image that allowed me to flash it but I still cannot mount anything in recovery? Any help would be nice
Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol
n3td3v said:
Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol
Click to expand...
Click to collapse
Folks, A quick search would have led ya here : http://forum.xda-developers.com/showthread.php?t=2183910&page=4 This is a known issue with both TWRP and CWM recoveries on newer S3's. Devs are working on it to find a solution. Just a matter of being patient and waiting. IF you just want root access, you can odin a pre-rooted rom to the phone with no issues. You'll atleast have root at that point. Just unable to change rom/kernels on the fly.
I achieved root with virtually no issues but thank you for the link!
Sent from my SPH-L710 using xda premium
Of all the things I have screwed up, I can't believe my first post asking for help is this one. I have been rooting and installing custom ROM's since the EVO. Always found the help I needed in someone else' thread. But this has me stumped.
I am a ROM jumper. Do it all the time. Yesterday, I was having some performance issues with my Note2 so I thought I would do a full wipe and try out another ROM. I also wiped my internal storage. My recover at that time was philz_touch_6.19.3-t0ltetmo. Somehow, I ended up wiping everything and I couldn't boot into anything other than Download mode.
Still no biggie. Wait until I got home and I would flash some with via Odin on my Windows netbook. It never worked. It would maybe get to 25% complete and hang. I left it running for about an hours with no results. Then I moved to my Linux desktop and installed Heimdall. Used that to put philz_touch_6.19.3-t0ltetmo back on the device. Then I installed cm-10.2-20140309-NIGHTLY-t0ltetmo.zip via sideload.
Stuck on smiling robot with a circle.
So I sideloaded CARBON-KK-NIGHTLY-20140302-0859-t0ltetmo.zip. Stuck on the logo there too. aokp_t0ltetmo_kitkat_nightly_2014-02-25.zip same thing. I try pushing the ROM's instead of sideloading. No luck.
So I am thinking that maybe I got a bad philz recovery. Redownload that, and go through the same list of roms. Nothing. OK... so maybe philz has become a POS for some reason on my phone. I try openrecovery-twrp-2.7.0.0-t0ltetmo.zip and repeat all the steps above. Wiping and sideloading, then wiping and pushing... stuck on logo.
I have to say I am stumped. I am losing nerd cred by asking for help, but dammit I am stumped. Any help appreciated.
Most phones have been recovered by flashing stock image, you can give it a shot.
Sent from my SGH-T889 using xda app-developers app
ciphercodes said:
Most phones have been recovered by flashing stock image, you can give it a shot.
Click to expand...
Click to collapse
Eww. Does that have to be flashed via Odin/Heimdall or can I use my established recovery? Also, I looked at some of those earlier and they are all in ZIP format. Odin wants TAR.MD5. Is it as simple as unziping and then tar-ing? I don't see an option to TAR.MD5.
marriedman said:
Eww. Does that have to be flashed via Odin/Heimdall or can I use my established recovery? Also, I looked at some of those earlier and they are all in ZIP format. Odin wants TAR.MD5. Is it as simple as unziping and then tar-ing? I don't see an option to TAR.MD5.
Click to expand...
Click to collapse
The easiest option would be to flash the tar.md5 file using ODIN.
If you are 4.3 bootloader you can flash this MrRobinson's ROM
http://www.androidfilehost.com/?fid=23252070760975435
If you are 4.1.2 bootloader you can flash this ROM, download link on post#1
http://forum.xda-developers.com/showthread.php?t=2636552
If you plan to flash it using Heimdall you will have to first extract the tar.md5 file and then flash all ROM components.
Your command should be something like this, please note I have not tried flashing using Heimdall so I am not 100% it will work.
sudo heimdall flash --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img --RADIO modem.bin
ciphercodes said:
The easiest option would be to flash the tar.md5 file using ODIN.
If you are 4.3 bootloader you can flash this MrRobinson's ROM
http://www.androidfilehost.com/?fid=23252070760975435
If you are 4.1.2 bootloader you can flash this ROM, download link on post#1
http://forum.xda-developers.com/showthread.php?t=2636552
Click to expand...
Click to collapse
Good stuff, thank you cipher.
Perhaps I am missing something here though. I went to check which version bootloader I have. I just assumed I would have 4.3 since I have been running JB & KK rom's for the past month or so; but I wanted to double check. When I boot into recovery, it doesn't show it there. When I boot into download mode, it doesn't show it there either. Where should I be seeing the version number?
When you boot into download mode do you see KNOX Warranty Void below system status ?
If not then your phone is not on 4.3 bootloader.
Sent from my SGH-T889 using xda app-developers app
Yes, it shows KNOX WARRANTY VOID: 1
So then I have 4.3. Thanks for the info. When I get home tonight, I will try and flash MrRobinson's ROM then report back. Thank you for the help & I will post my results then.
Well, that took care of it. I was able to use MrRobinson's ROM & Heimdall. I did have to download a PIT file, but that was easily found here on xda. Within minutes I had the gawd awful Samsung TW blooping and making stupid noises. Went ahead and flashed TWRP and I am downloading CarbonRom now.
Thanks for the help cipher. It was driving me nuts.
um... mark as solved?
I tried to edit my original post to mark it as solved, but there isn't an option. How do I change my title?
Well, I spoke too soon. I just discovered that I have no cell service. Went to look and found I have no IMEI # anymore. WTF?
Looks like you flashed a modem for a different device.
No worries, just flash the modem from Mr Robinsons ROM and that should take care of it.
Sent from my SGH-T889 using xda app-developers app
I wish it were that simple. I just reflashed MrRobinsons and it is back to Samsung recovery and rom. Still no IMEI. I am going to go full retard and flash the one from SamMobile. I'll erport back later.
Mrrobinsons ROM is the stock rom, it's just root injected and Knox-free.
Try KIES emergency recovery method.
You can find link for procedure in this forum in one of the posts.
Sent from my SGH-T889 using xda app-developers app
Just saw this and I am on my way to work. With no Admin priviledge there, I will have to try this when I get home.
I appreciate the time you have taken to help me cipher.
OKay, I downloaded Kies and it saw my phone. However, it says my phone is fine and will not do an emeregency recovery. After searching on here some more, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2261153
It's possible that Emergency Recovery is no more. I am just about done with this phone. It's been three days and I need a working phone again.
marriedman said:
Of all the things I have screwed up, I can't believe my first post asking for help is this one. I have been rooting and installing custom ROM's since the EVO. Always found the help I needed in someone else' thread. But this has me stumped.
I am a ROM jumper. Do it all the time. Yesterday, I was having some performance issues with my Note2 so I thought I would do a full wipe and try out another ROM. I also wiped my internal storage. My recover at that time was philz_touch_6.19.3-t0ltetmo. Somehow, I ended up wiping everything and I couldn't boot into anything other than Download mode.
Still no biggie. Wait until I got home and I would flash some with via Odin on my Windows netbook. It never worked. It would maybe get to 25% complete and hang. I left it running for about an hours with no results. Then I moved to my Linux desktop and installed Heimdall. Used that to put philz_touch_6.19.3-t0ltetmo back on the device. Then I installed cm-10.2-20140309-NIGHTLY-t0ltetmo.zip via sideload.
Stuck on smiling robot with a circle.
So I sideloaded CARBON-KK-NIGHTLY-20140302-0859-t0ltetmo.zip. Stuck on the logo there too. aokp_t0ltetmo_kitkat_nightly_2014-02-25.zip same thing. I try pushing the ROM's instead of sideloading. No luck.
So I am thinking that maybe I got a bad philz recovery. Redownload that, and go through the same list of roms. Nothing. OK... so maybe philz has become a POS for some reason on my phone. I try openrecovery-twrp-2.7.0.0-t0ltetmo.zip and repeat all the steps above. Wiping and sideloading, then wiping and pushing... stuck on logo.
I have to say I am stumped. I am losing nerd cred by asking for help, but dammit I am stumped. Any help appreciated.
Click to expand...
Click to collapse
Ok first off, dont have tmobile, but i do have a note (verizon)
What do you mean when you say you are "sideloading" "pushing" a ROM.. Bc normally in recovery you "flash" a rom.
So let's make sure you are doing just that..?
If you are "flashing" a rom in recovery and it installs and you reboot and you are stuck.. thats a different issue..
I would recommend getting your stock Odin tar and flashing it..Make sure it contains a boot.img and if you guys use a pit file.. use that as well..
Post here with some answers and results..Lets see if we can get you back in buisness..
I have HARD bricked my phone, fired eMMC, softed bricked..pretty much been through everything so hopefully we can figure it out!:good:
The main thing is DON'T get frustrated.. I know it's hard but that when you make mistakes and PANIC
lacoursiere18 said:
What do you mean when you say you are "sideloading" "pushing" a ROM.. Bc normally in recovery you "flash" a rom.
So let's make sure you are doing just that..?
Click to expand...
Click to collapse
Originally, I could not boot into any rom. I could get into recovery. In order to get a rom onto the phone, I could download the zip file to my computer and inside the recovery turn on sideload to move the file to the phone and flash. And Even then I never got any of the roms to get past the boot logo. Cyanogenmod, Carbon-rom, AOKP... none of them.
I would recommend getting your stock Odin tar and flashing it..Make sure it contains a boot.img and if you guys use a pit file.. use that as well..
Click to expand...
Click to collapse
Yup, I did that. I tried doing it through Heimdall since I am a Linux guy. I can install a stock or stock based rom, but there is never a IMEI number. From what I can tell, the EFS partition is just gone & I never backed it up. I lost the IMEI and it is not coming back.
The main thing is DON'T get frustrated.. I know it's hard but that when you make mistakes and PANIC
Click to expand...
Click to collapse
Oh, I agree. I stepped away from it for about 8 hours a day while at work. Thats when I did most of my reading though. I am pretty sure this is going up for sale on ebay this week. I already bought a new phone. Thank you for taking the time to reply though.
marriedman said:
Originally, I could not boot into any rom. I could get into recovery. In order to get a rom onto the phone, I could download the zip file to my computer and inside the recovery turn on sideload to move the file to the phone and flash. And Even then I never got any of the roms to get past the boot logo. Cyanogenmod, Carbon-rom, AOKP... none of them.
Yup, I did that. I tried doing it through Heimdall since I am a Linux guy. I can install a stock or stock based rom, but there is never a IMEI number. From what I can tell, the EFS partition is just gone & I never backed it up. I lost the IMEI and it is not coming back.
Oh, I agree. I stepped away from it for about 8 hours a day while at work. Thats when I did most of my reading though. I am pretty sure this is going up for sale on ebay this week. I already bought a new phone. Thank you for taking the time to reply though.
Click to expand...
Click to collapse
Have you tried flashing the latest firmware, and if yes is this where you got it?
http://forum.xda-developers.com/showthread.php?t=2102380
Also did you read post #2 about going back into recovery, do a factory reset and reboot?
And were you getting these roms that would loop you in this forum, just making sure i know it may sound stupid..
Also, what was the estimated time you were waiting for them to boot..5mins, 10mins, 20mins.. Some take longer than others..
The only other thing i could suggest is JTAG services, by MobileTechVideos, the owner's name is Josh, stand up guy, and I belive it much cheaper than buying a new device =)
lacoursiere18 said:
Have you tried flashing the latest firmware, and if yes is this where you got it?
http://forum.xda-developers.com/showthread.php?t=2102380
Also did you read post #2 about going back into recovery, do a factory reset and reboot?"
Click to expand...
Click to collapse
Yep & yep. I also tried MrRobinsons root injected rom before going this route.
And were you getting these roms that would loop you in this forum, just making sure i know it may sound stupid..
Also, what was the estimated time you were waiting for them to boot..5mins, 10mins, 20mins.. Some take longer than others..
Click to expand...
Click to collapse
I have had some take as long as 20 minutes before, but that was rare. This time, I actually fell asleep and when I woke up in the morning, it was still on the animated boot logo and hot as hell. Still going though. So it was at least 6 hours thst timr.
The only other thing i could suggest is JTAG services, by MobileTechVideos, the owner's name is Josh, stand up guy, and I belive it much cheaper than buying a new device =)
Click to expand...
Click to collapse
I've not heard of this, I'll look them up. Thanks!
I have the SGH-M919
I've rooted my phone and was running a GE rom
Everything was fine for MONTHS
Got in my car and plugged my AUX cable to my phone for music and the phone froze.
Force rebooted the phone and it started boot looping.
Rebooted to recovery (TWRP) and TRIED to wipe dalvik and cache and it FAILED, said it couldn't mount dalvik
Rebooted to recovery again and wiped all partitions and this time it worked so I proceeded to re-install GE rom, still bootlooping
Came home and tried to use ODIN to flash M919UVUAMDL and it failed.
Tried ODIN to flash M919UVUEMK2, also failed (sorry don't have the error messages right now)
Rebooted phone into download mode again and phone said there was an issue and to use Kies to recover
Installed Kies and started emergency recovery and that went through fine and the phone finished and STILLLLLLL BOOT LOOPS !!!!!!!!!!!
Copied the file that Kies downloaded (M919UVUFNB4) and tried ODIN again to flash that and it flashes fine but STILLL BOOT LOOPS
Obviously my Knox warranty flag is tripped and I don't have the money for the insurance right now.... so PLEASE FOR THE LOVE OF BOB does anyone have any other diagnostic tips or tricks to help me figure out why the F this phone is boot looping.
53 views and no replies.... come on people... someone HAS to have something that might help..
Anyone know if ANY possible way to reset the knox warranty void flag ?
avelis26 said:
53 views and no replies.... come on people... someone HAS to have something that might help..
Anyone know if ANY possible way to reset the knox warranty void flag ?
Click to expand...
Click to collapse
Only Samsung can reset your Knox flag. You can't expect instant responses here. People read and answer the questions they know how to. Not doing a full wipe before installing a different ROM often causes soft bricks and bootloops. I would start there although that doesn't explain why you couldn't mount Dalvik. Try a different recovery. Many people have had trouble with TWRP. Philz Touch works well if you haven't already tried it.
Sent from my SGH-M919 using xda app-developers app
I literally just had the exact same problem as you. I googled and found http://forum.xda-developers.com/showthread.php?t=2265477, then googled some more and found my .tar file for my phone, then odined back to stock 4.2.2. It took 20 min.
lalec said:
Only Samsung can reset your Knox flag. You can't expect instant responses here. People read and answer the questions they know how to. Not doing a full wipe before installing a different ROM often causes soft bricks and bootloops. I would start there although that doesn't explain why you couldn't mount Dalvik. Try a different recovery. Many people have had trouble with TWRP. Philz Touch works well if you haven't already tried it.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
1. Samsung WON'T reset my flag... they won't even TOUCH the phone in any way shape or form. I spent almost two hours dealing with them and being honest about the situation. And they STILL won't do anything at all. The rep I was speaking too even said the first thing they do is check that flag and if its popped, they put it back in the box and send it back with no further action. So I will not buy form Samsung ever again.
2. I'm not expecting instant responses at all and nothing I said should have been interpreted at such. I made the comment of 53 views in 4 hours and not a single reply ... I was hoping for a better ratio of responses than that.
3. Where are you getting "Not doing a full wipe before installed a different ROM..." I never said that I didn't... and if you read what I took the time to organize neatly, I specifically state that full wipe was what I tried BEFORE re-installing the SAME rom.
4. Can't try a different recovery if I can't even get the stock factory image to do an initial boot.
cybervyrus8587 said:
I literally just had the exact same problem as you. I googled and found http://forum.xda-developers.com/showthread.php?t=2265477, then googled some more and found my .tar file for my phone, then odined back to stock 4.2.2. It took 20 min.
Click to expand...
Click to collapse
Which one did you flash ?
M919UVUFNB4
M919UVUEMK2
M919UVUAMDL
M919UVUAMDB
I've tried #3 but it gives me an auth failure....
Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love
TigerDNA said:
Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love
Click to expand...
Click to collapse
lol ummm ok I'm glad to hear that but how would flashing a recovery fix the fact that the factory stock image won't even work Not being a ****... I really do want to know
avelis26 said:
lol ummm ok I'm glad to hear that but how would flashing a recovery fix the fact that the factory stock image won't even work Not being a ****... I really do want to know
Click to expand...
Click to collapse
Post deleted
☞ Sent from here ☜
baseballfanz said:
Post deleted
☞ Sent from here ☜
Click to expand...
Click to collapse
Sooooo umm what ?
Anyway... I flashed PhilZ on my phone, did full wipe, tried installing the same GE rom I was using... didn't work.
Tried installing stock rom, didn't work.
Tried flashing M919UVUFNB4 via ODIN... and it flashes fine but again, first boot wont work.
Ok so .... I guess installing PhilZ... then full wipe, then flashing M919UVUFNB4 TWICE back to back did the trick.... no freaking clue how but it worked
I spoke too soon. Went through first boot. Got all the way to the end setup and then it rebooted on its own ... and now its stuck in a boot loop again
avelis26 said:
Sooooo umm what ?
Anyway... I flashed PhilZ on my phone, did full wipe, tried installing the same GE rom I was using... didn't work.
Tried installing stock rom, didn't work.
Tried flashing M919UVUFNB4 via ODIN... and it flashes fine but again, first boot wont work.
Click to expand...
Click to collapse
Since your using philz, choose install new ROM, then go to advanced and wipe dalvik, THEN go to mounts and select the one close to the bottom, wipe SD/data or something..... This will wipe your internal SD, OK so then install your rom and reboot.....
I am starting to think you flashed a non GE kernel and didnt realize it You just got to give the phone some love, thats all. It knows when your upset you know.
TigerDNA said:
Since your using philz, choose install new ROM, then go to advanced and wipe dalvik, THEN go to mounts and select the one close to the bottom, wipe SD/data or something..... This will wipe your internal SD, OK so then install your rom and reboot.....
I am starting to think you flashed a non GE kernel and didnt realize it You just got to give the phone some love, thats all. It knows when your upset you know.
Click to expand...
Click to collapse
lol
The weirdness continues
sooo it started boot looping again. Then I rebooted to recovery (which obviously after flashing NB4, its no longer PhilZ) and did factory reset. Now its working again with latest firmware.
Also I flashed the GE rom from HERE in XDA and used it for like 2 or 3 months then it suddenly stopped working so I don't think the kernal was the issue... I'm so freaking confused
avelis26 said:
lol
The weirdness continues
sooo it started boot looping again. Then I rebooted to recovery (which obviously after flashing NB4, its no longer PhilZ) and did factory reset. Now its working again with latest firmware.
Also I flashed the GE rom from HERE in XDA and used it for like 2 or 3 months then it suddenly stopped working so I don't think the kernal was the issue... I'm so freaking confused
Click to expand...
Click to collapse
Flash something else, GE is boring, Flash something crazy like Slim or something, that might work... Possibly it could be a bootloader issue, did you ever get on the MK2? Maybe you got one of the female phones. Sammy made some by mistake. they can be real finicky every now and then, like they work just fine most of the time, but about once a month or so they just crap out. Could be that too.
TigerDNA said:
Flash something else, GE is boring, Flash something crazy like Slim or something, that might work... Possibly it could be a bootloader issue, did you ever get on the MK2? Maybe you got one of the female phones. Sammy made some by mistake. they can be real finicky every now and then, like they work just fine most of the time, but about once a month or so they just crap out. Could be that too.
Click to expand...
Click to collapse
No never got MK2... went straight to NB4
And I LIKE GE lol...
Well whatever happened it seems stable again now currently on stock NB4
Next thing to check is if the knox warranty flag is still tripped... Do you know how to do that ?
Yea your Knox flag is tripped alright, you have zero chance if ever getting back to 0x0.... Nobody knows how to do that brother.
Sent from my GT-I9505G using xda app-developers app
avelis26 said:
No never got MK2... went straight to NB4
And I LIKE GE lol...
Well whatever happened it seems stable again now currently on stock NB4
Next thing to check is if the knox warranty flag is still tripped... Do you know how to do that ?
Click to expand...
Click to collapse
Just put the phone in download mode. Power off then volume up, home and power. You'll see it when you get into download mode.
TigerDNA said:
Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love
Click to expand...
Click to collapse
Philz's and TWRP both had small glitches on the GS4 4.2.2 Stock Rom.
I downloaded and installed the OUDHS-Recovery-jfltetmo-1.0.3.3.tar and have it all PERFECT now! You can search using exactly that filename and download it for your use. IT IS THE flashable Recovery Version.
I can, using Rom Manager, NAME THE BACKUP before booting into recovery, and it makes the backup just as I named it!
I can also recover using Rom Manager, and visually select what backup file I want to restore to, again, before booting into recovery!
CWM type backups take longer then TWRP backups to complete, but I have not had any instance that a backup I made couldn't be restored.
I did have that problem using "TWRP" and "On Line Backup". (No longer do I trust using those)
Hope this info helps your decision!
Good Luck and Aloha!
Hello. I tried to root my Samsung Galaxy Tab 3 - T210 and i think i really screwed it up. I did not make any backup, that was mistake NR one.
I got clock work mode up and running but i cant install any ROM, have tried The original Firmware, RocketTab, Cyanogenmod and cant pass the installation process and i think i cant turn back cause i got no backup and no way to install it again.
When i run any of these ROMs i get this error :
format() expects 4 args, got 5
Click to expand...
Click to collapse
No matter what i do, im a a bit scared know cause i think i am really close on destroying the tablet.
Can any one help me ? give me tips ?
CWM that i am running is : T210_CWM.6.0.4.7.recovery that i downloaded frome the XDA forum.
A,
panic solves nothing.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi/
when in doubt choose the most recent. zip or tar for odin.
for a rom i suggest svelte to get things straight.
then go from there.
m
1
Thank you for a quick answer, so i should change out CWM for Philz Touch ?
What is "Svelte" ? have no clue what that means.
What to have 110% solid answer before i go wreck some thing more.
Ah, of course.
Audriuss95 said:
Thank you for a quick answer, so i should change out CWM for Philz Touch ?
What is "Svelte" ? have no clue what that means.
What to have 110% solid answer before i go wreck some thing more.
Click to expand...
Click to collapse
I hear you, okay,
svelte rom thread - http://forum.xda-developers.com/showthread.php?t=2722582
great rom, minimal issues. philz advanced recovery is cwm with a good touch interface and more and very helpful options.
So yes, switch. All else is almost always solveable as long as your recovery is solid.
m
1
moonbutt74 said:
A,
panic solves nothing.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi/
when in doubt choose the most recent. zip or tar for odin.
for a rom i suggest svelte to get things straight.
then go from there.
m
Click to expand...
Click to collapse
moonbutt74 said:
I hear you, okay,
svelte rom thread - http://forum.xda-developers.com/showthread.php?t=2722582
great rom, minimal issues. philz advanced recovery is cwm with a good touch interface and more and very helpful options.
So yes, switch. All else is almost always solveable as long as your recovery is solid.
m
Click to expand...
Click to collapse
To be 100% sure when people say recovery they mean the programs like CWM or TeamWin and so on right ?
Is it bad for the device to change often the recovery software ? cause i have done that couple of times, started with TeamWin and later on ended up with CWM.
But the thing is that the problem is the installation process, it does not matter what ROM i use i get still the same error.
And for the Philz Touch could you copy the name of the link that i should download, they all look the same and way more links that i am used to.
Audriuss95 said:
To be 100% sure when people say recovery they mean the programs like CWM or TeamWin and so on right ?
Is it bad for the device to change often the recovery software ? cause i have done that couple of times, started with TeamWin and later on ended up with CWM.
But the thing is that the problem is the installation process, it does not matter what ROM i use i get still the same error.
And for the Philz Touch could you copy the name of the link that i should download, they all look the same and way more links that i am used to.
Click to expand...
Click to collapse
The reason you can't install any rom is because you do not have the latest version of CWM installed. You should always install the newest version when you install any recovery.
The newer roms are using an updater-script that will not work on CWM 6.0.4.7. Install an updated recovery and then install the rom that you want.
Sent from my SM-T310 using Tapatalk
Audriuss95,
Is it bad for the device to change often the recovery software ? cause i have done that couple of times, started with TeamWin and later on ended up with CWM.
To answer your question no yes maybe. Travel around through XDA and read/learn and you will understand.
as for philz i would try this one https://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi/philz_touch_6.44.9-lt02wifi.zip
in general find a recovery that works for you and stick with it until an update is actually called for.
m
If I were you, I would unroot and return to stock using ODIN first before I try anything else. If you need instructions, Google "unroot and return to stock using ODIN".
1
gr8nole said:
The reason you can't install any rom is because you do not have the latest version of CWM installed. You should always install the newest version when you install any recovery.
The newer roms are using an updater-script that will not work on CWM 6.0.4.7. Install an updated recovery and then install the rom that you want.
Sent from my SM-T310 using Tapatalk
Click to expand...
Click to collapse
What is then the newest version that i can use on this device ? could you maybe throw a link at me ?
moonbutt74 said:
Audriuss95,
Is it bad for the device to change often the recovery software ? cause i have done that couple of times, started with TeamWin and later on ended up with CWM.
To answer your question no yes maybe. Travel around through XDA and read/learn and you will understand.
as for philz i would try this one
in general find a recovery that works for you and stick with it until an update is actually called for.
m
Click to expand...
Click to collapse
Thank you for the answear. gone try a little bit more with the recovery i already have and update it like gr8nole said. Maybe that could be my big problem.
ikeny said:
If I were you, I would unroot and return to stock using ODIN first before I try anything else. If you need instructions, Google "unroot and return to stock using ODIN".
Click to expand...
Click to collapse
Yeah i have thought of that but the thing is i never took a backup so i cant go back atleast from what i read on google.
Audriuss95 said:
Yeah i have thought of that but the thing is i never took a backup so i cant go back atleast from what i read on google.
Click to expand...
Click to collapse
Without a backup, you will lose your data and files. But you can restore, since you can download the firmware from SamMobile.
Audriuss95 said:
What is then the newest version that i can use on this device ? could you maybe throw a link at me ?
Click to expand...
Click to collapse
6.0.4.9 is the latest.
http://www.androidfilehost.com/?w=files&flid=12949
Choose the one with "flashable" in the name and then flash it using your current CWM recovery; then reboot recovery.
1
ikeny said:
Without a backup, you will lose your data and files. But you can restore, since you can download the firmware from SamMobile.
Click to expand...
Click to collapse
I downloaded the FirmWare from SamMobile still get an error. the one that a wrote above.
gr8nole said:
6.0.4.9 is the latest.
Choose the one with "flashable" in the name and then flash it using your current CWM recovery; then reboot recovery.
Click to expand...
Click to collapse
Ok i am going to try out that file.
I use that flashable file like i would install ROM ? right but it on SD card and not use ODIN or ?
1
I updated to to the newest CMW tried the CM mod and got an error but it only said "Installation Aborted" the i tried to install the RocketTab 3.1 and it worked. I downloaded it from the this thread [ROM][SM-T210/T210R][Jan 30] RocketTab v3.1 Lite / Full / MODs
But i would rather like to have CM what can do ?
hey
Audriuss95 said:
I updated to to the newest CMW tried the CM mod and got an error but it only said "Installation Aborted" the i tried to install the RocketTab 3.1 and it worked. I downloaded it from the this thread [ROM][SM-T210/T210R][Jan 30] RocketTab v3.1 Lite / Full / MODs
But i would rather like to have CM what can do ?
Click to expand...
Click to collapse
good to hear you got it sorted. CM just isn't happening yet. just watch the forum like a hawk like everyone else is...:cyclops:
If your worried about destroying your tab you prolly shouldn't have come to mod it.I know sounds like a douche bag thing to say but even putting on the flash or roms that go with the tab can destroy your tab if done improperly or even if they glitched while flash which does happen or even worse power outage when flashing.
1
moonbutt74 said:
good to hear you got it sorted. CM just isn't happening yet. just watch the forum like a hawk like everyone else is...:cyclops:
Click to expand...
Click to collapse
So i should put the CM mod aside ?
piercejpierce said:
If your worried about destroying your tab you prolly shouldn't have come to mod it.I know sounds like a douche bag thing to say but even putting on the flash or roms that go with the tab can destroy your tab if done improperly or even if they glitched while flash which does happen or even worse power outage when flashing.
Click to expand...
Click to collapse
Nono it is okey to say something like this, but the thing is i like to learn this stuff, took me about 3 days to learn how to flash a BIOS on a computer but when i got the hang of it i learned it.
I am scared of destroying the tablet but how else would i learn ? cause reading does not always help But i got it back up again. And i knew when to ask for help.
But the RocketTab looks to work well at least for know, but would love CM mod couse i have it on my S4 and when and with the RocketTab i only get android version 4.1.2
1
Thank you for the fast help, the tablet is up and running, gone skip for know trying to use CM mod.