hi guys i need some help i downloaded cyanogen 11 lastnight just because my phone kept prompting me to update and i was rooted. I installed it and immediately noticed that i can not see my sd card, after researching i saw a couple of people was having the same issue. I tried to recover from the backup i made and it make my phone get stuck in a endless loop after about 10 hours of trying to get in recovery and failing it finally let me in and started loading the rom again. I keep trying to replace the rom with other roms and the phone will not see any of roms to push i tried odin and that failed as well . can someone help me get this stupid rom off my phone i tried everything.
Darkmanx said:
hi guys i need some help i downloaded cyanogen 11 lastnight just because my phone kept prompting me to update and i was rooted. I installed it and immediately noticed that i can not see my sd card, after researching i saw a couple of people was having the same issue. I tried to recover from the backup i made and it make my phone get stuck in a endless loop after about 10 hours of trying to get in recovery and failing it finally let me in and started loading the rom again. I keep trying to replace the rom with other roms and the phone will not see any of roms to push i tried odin and that failed as well . can someone help me get this stupid rom off my phone i tried everything.
Click to expand...
Click to collapse
Which recovery are you running?
joeyhdownsouth said:
Which recovery are you running?
Click to expand...
Click to collapse
I got it, I finally got stock a rom to load via Odin but it was getting stuck on the Samsung screen so I rooted it before it even let me in. Then i did a wipe and it started up and now all is well stock 4.3 rooted. This reminded me why i always choose stock rooted roms
Related
Hello,
Well, hopefully someone can help me out with an issue. While I've rooted and flashed phones before this, I probably know just enough to be dangerous. So, I was planning on moving back to my EVO 4g and thought I'd like to put ICS or JB on the phone to use as my normal device. So Sunday, I started playing with different ROMs in the forums. After flashing several ROMS I had an issue start. The phone would go through the White 'HTC EVO 4g' boot screen, stay there a moment and then reboot. I tried to reflash that ROM and had no luck. The only way to get out of this loop is to pull the battery. After searching on the website all week, I've tried several ideas, however nothing works. The last thing I did was to basically go through the process of rooting the phone again. After I did the fastboot command, I put the su-bin-3.0.3.2-efghi-signed.zip file onto the SD card and used the recovery tool to install the ROM. After I did this, I restarted the device and no joy. However now the phone will only boot up to HBoot screen. I can get to recovery, however I can not put any ROMs on the phone. Any help would be appreciated. Thanks in advance.
Rob
Are you sure you got a custom recovery or a ROM installed? You've only mentioned su binary zip which, I believe, isn't either of the previous.
Robobob1221 said:
Are you sure you got a custom recovery or a ROM installed? You've only mentioned su binary zip which, I believe, isn't either of the previous.
Click to expand...
Click to collapse
Actually, No. So I went back and looked at the directions I was following and realized that the 'su-bin-3.0.3.2-efghi-signed.zip' file was not a ROM or recovery file. When it was flashed onto the phone the stock rom was still on the phone. So ... I sent the 'TeamDIRTremicsUXv1.3' ROM over to the SD card and flashed it ..... IT WORKED .... thanks for the help!!!!!
Rob
Good to hear!
Enjoy the Team D.I.R.T goodness!!
Happy flashing!
An enviousOG
I have a serious problem. I have a Samsung Galaxy s II Tmobile for about a year now I have had it rooted since day one with not one problem with it. I mostly have had installed custom roms is all. I Just recently updated to CM10.1 nightlys with no trouble. I thought I would update the custom recovery since its been a while I went from 5.0.2.7 and updated to 6.0.2.8 and this is where everything went wrong. my phone went into a bootloop at first wouldn't load at all I went into recovery restored to a cm 10 which was working before which now is doing a boot loop. and i restored back to 2.3.5 rooted and that worked. but with some serious problems. I can't download anything like from the web or play store at all I keep getting this error code 492. I was thinking ok well I'll just put a fresh copy of cm10.1 back on the phone flashing it through recovery and nothing it froze. I played around with this new recovery and found out that I can't install anything through recovery can't fix permissions won't format won't wipe cache or factory reset and it won't even reboot the phone the only thing i got it to do was restore to 2.3.5. well I thought ok well I'll just start over again by unrooting the phone and start at square one again. no problem as the phone isn't bricked but when I hooked it to the computer now its not recognizing it. it comes up as unknown device which worked yesterday and never had a problem before i tried uninstalling drivers off my computer reinstalling them to no success. however I thought If I somehow get rom manager back on the phone i can reinstall 5.0.2.7 back on which i did come up with the idea to use kies air for that which did work. but I couldn't get back to 5.0.2.7 by doing that does anybody have any suggestions that can help me out my phone is working i can do everything that it is suppose to do make call connect to the mobile web, wifi but i want back on my custom rom can anybody help thanks
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
cvall91 said:
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
Click to expand...
Click to collapse
I thought rooted phones weren't allowed to update via Kies or OTA.
allenjthomsen said:
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I guess I'll try to download it again and see if that works. Do you know if that's through Kies or through manually downloading it then using Odin?
Techngro said:
I thought rooted phones weren't allowed to update via Kies or OTA.
Click to expand...
Click to collapse
Well it seemed to update for me. At least the verification process went through. I used Wanam Xposed and had the fake system status thing checked. Either way something went wrong and didn't finish the updating process and got stuck at boot logo with no recovery options.
The OTA update did not work though. I was able to get the update downloading after Wanam, but once the download finished, the update failed before trying to install. Did not try OTA again though I just went to Kies, then Odin. But all 3 methods failed.
Hey,
I had AOSP installed on my ascend p6, everything working no problems at all.
Suddenly when I was a week on vacation when my battery died it wouldn't get passed the rom loading screen.
I have TWRP 2.7 and have wiped everything and everything over and over but nothing is working. I am now trying to install The lastest aosp sincde OMNI and CM11 didn't work.
Any help how to fix this? it keeps happening at every rom I install.
Little update:
I just tried reverting from twrp 2.7 to stock boot and recovery and I think I just bricked my device Can;t get passed the huawei ascend screen.
I wanted to reinstall the 118cn from stock recovery. is there anyway to fix this? Thank you!
UPDATE: Okay somehow after rebooting it around 20 times with fastboot, recovery and other combinations it is now booting I think. Praise the lords. It is now optimizing the apps
I have no idea what I did but I will post an update when it is done optimising
UPDATE UPDATE: Okay the weirdest thing just happened and I don't get this at all... I have wiped my whole phone like 5 times. with itsto and exsto. but somehow I now boots with all my apps, settings and launcher intact and inplace... I even installed multiple roms trying to make it work. WHAT IS THIS MAGIC?!
I know I shouldnt do this but I am going to re-install twrp 2.6.*.* and then pushing it to 2.7. Wish me luck! (following the excact instructions to make it work haha)
UPDATE UPDATE UPDATE: Okay, After seeing the wi-fi not turning on I tried rebooting my phone now it is stuck at the huawei ascend screen.
TomTheTiger said:
Little update:
I just tried reverting from twrp 2.7 to stock boot and recovery and I think I just bricked my device Can;t get passed the huawei ascend screen.
I wanted to reinstall the 118cn from stock recovery. is there anyway to fix this? Thank you!
Click to expand...
Click to collapse
Jelly Bean China stock roms can brick device (lots of users on xda got their device bricked). If you wanted to unlock, best to use KK China.
warea said:
Jelly Bean China stock roms can brick device (lots of users on xda got their device bricked). If you wanted to unlock, best to use KK China.
Click to expand...
Click to collapse
Will try! I thought I was passed this haha. When It starts i'll try to figure out a way to install it probs trough adb fastboot. since I can't get to the recovery screen with buttons
Update: Okay I managed to boot recovery up trough adb, It automatically started installing the update.app package.
I am now hoping for the best, one good thing... My phone was luckily already in unlock state
UPdate: Succesfully flashed my phone the stock with unlocked bootloader!
UPDate: And now on omni rom Everything is working fine!
So This is my first time posting on any forum site for help, and i was refereed to XDA by my roommate. so what happened is a few months ago i asked my roommate to root my galaxy s3 SGH-I747, after he rooted it through odin and all seemed well, BUT we never could get the phone to recognize the root and was still unable to access any root functions. so after a few different attempts we gave up. i assumed that my roommate had removed the root (bad call) but never gave it any thought. a few days ago at&t started bugging me with a software update. i just hit ignore and it would pop up again in a few hours and the icon would never go away. so i gave in and started the update. i didnt pay the phone any attention while it "updated" but later that morning i went to turn it back on and it would get to the Samsung screen then the next screen but after that it goes black and vibrates. i showed it to my roommate and he informed me that it was never restored back to official frimware like i had previously assumed. and that it never should have received the update bc it was still on a custom frimware. we tried flashing the stock frimware back on the phone and every time it would fail the nand write. i believe it was updated to 4.4.2 before i received the update from AT&T and we tried many different ways too restore it i even tried the recovery in Kies 3 but all it says is "connecting" then connection failed. so far nothing has worked. i believe that the update contained android 5.0 and maybe that is the reason none of the other ways we tried worked. i have been researching for hours trying to find a similar case but nothing matches, and i cant find a single working solution that doesn't involve possible making it worse. i can access both the recovery and download modes. please any information or help would be greatly appreciated.
Flash a custom recovery such as Philz Touch via Odin, install cm10.2 via your custom recovery. This should get the phone booted so you can determine the bootloader version on your phone. The NAND error is due to the fact that you are trying to downgrade the bootloader in Odin. Don't flash anything with Odin until you determine the bootloader. Doing so could hard brick your phone.
audit13 said:
Flash a custom recovery such as Philz Touch via Odin, install cm10.2 via your custom recovery. This should get the phone booted so you can determine the bootloader version on your phone. The NAND error is due to the fact that you are trying to downgrade the bootloader in Odin. Don't flash anything with Odin until you determine the bootloader. Doing so could hard brick your phone.
Click to expand...
Click to collapse
firstly, thanks for the fast help. i did as you advised and flashed philz touch 6.15.4 which is the latest version from what i understand. that worked flawlessly. the problem now, is with cm10.2 every time ive tried to install it i get an error in /storage/sdcard1/cm-10.2.0-d2att.zip.
im sure im doing everything correctly. any ideas?
Try flashing an older CM11 ROM for the d2lte.
audit13 said:
Try flashing an older CM11 ROM for the d2lte.
Click to expand...
Click to collapse
thanks so much man youve been a big help that worked.