Hi ive installed multiboot rom from the play store and it went through the install possess and rebooted all seemed ok and fired up multiboot and it said I need to update hard boot kext so I updated and now it wont boot it gets stuck on the htc one splash screen. and I cant get in to my recovery manager it gets stuck on entering recovery. Is there a way to fix this prob. any input ould be great thanks.
Ok thanks for those who looked but I managed to fix my problem myself. What I did was to fastboot a fresh copy of twrp over and restore from a image I had backed up. Easy really but I panicked I suppose.
gimpchop said:
Ok thanks for those who looked but I managed to fix my problem myself. What I did was to fastboot a fresh copy of twrp over and restore from a image I had backed up. Easy really but I panicked I suppose.
Click to expand...
Click to collapse
It's good that you managed to fix the issue. Next time, you know what to do. Be careful before you flash anything on your phone.
Yer learned my lesson stupidly thought it would be safe as its a tested app with 5star reviews but something went wrong for me for some reason would still like multi rom but nervous now lol.
gimpchop said:
Yer learned my lesson stupidly thought it would be safe as its a tested app with 5star reviews but something went wrong for me for some reason would still like multi rom but nervous now lol.
Click to expand...
Click to collapse
From what I understand, it doesn't work with the M8. There is an unofficial MultiROM TWRP recovery out there made by XDA member @Captain_Throwback that you can get for the M8.
Go here for the download and instructions.
Oh ok thanks for the info it duz say in the app info it is icompatable with the m8 though.
Related
hate to ask for help bc u can usually find the answer somwhere....if my phone IS really bricked would love someone to tell me that so i can move on. seemed to have read that if it comes on then its not bricked..idk. ive rooted, flashed new roms and flashed it back completely stock.
i bricked it by attemting to flash it to boost...wrote nv items and zero'd out the meid. was looking for the esn so i could do the same, got a few of em.....phone fell battery flew..now i cant get past the first white htc screen...now this is where things get funky. a step of the guide i was following required root so i did n i saw cwm.. wen i got the bootloop i wasnt really worried at first bc i kne i could try a few things. well that didnt last long. booted into hboot n it said s-on..? then it wouldnt let me in recovery, just rebooted to the bootloop. i tried runnig unrevoked agn even tho i couldnt boot...couldnt read the phone. put the pb13img on sd card and it went thru its updating process n asked to reboot. reboots in same bootloop. next i tried runnig RUU..it runs and reboots my phone to the same bootloop...is there anyway to restore the ORIGINAL nv items and meid/esn...since these are the only things other than running unrevoked that ive changed i think thats where my problem lies. any help would be greatly appreciated.
Which radio is currently flashed on your phone? I had this issue once, I had to flash back to the 7.28 radio to get my phone to boot.
damn when i saw this post, i thought it was my post! i did almost the exact same thing and its acting almost the same as your phone. i did the ruu and it worked on the one posted in my thread, ran through and all but nothing. how would i done grade the radio?
i never flashed a radio...hboot says 2.15.00.07.28..
lol waxworks i saw ur post also... started reading and we pretty much did the same thing on pretty much the same step of flashing to boost...mad as hell too stuck with this incognito for awhile smh..
is there anyway to flash a nandroid without being able to get into cwm? idk man jus not looking good.
Reading your post not sure if you used the stock image and tried to update using the hboot menu.There is a thread 5 vibe fix that may help you get a rom image back to your phone
Vernox701 said:
Reading your post not sure if you used the stock image and tried to update using the hboot menu.There is a thread 5 vibe fix that may help you get a rom image back to your phone
Click to expand...
Click to collapse
Do you happen to have link? I'm on tapatalk and there no search
waxworkz said:
Do you happen to have link? I'm on tapatalk and there no search
Click to expand...
Click to collapse
I believe this is what you're looking for:
http://forum.xda-developers.com/showthread.php?t=1110865
no fix for this?...anyway to get s-off only being able to use fastboot?
strive53 said:
no fix for this?...anyway to get s-off only being able to use fastboot?
Click to expand...
Click to collapse
I think we have bricks! I tried to do some other method that involved running a script and cmd prompts. Didn't do anything as I am also "S" on. I think all the fixes are for "S" off.
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Try flashing the stock tar in odin if nothing else works.
DroidGnome said:
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Click to expand...
Click to collapse
Just flash the stock tar ur downloading in Odin. Ur fine even if you managed to Bork recovery as long as u can still get into dl mode ur ok
I've haven't seen this problem on the Sprint variant yet but it definitly sounds like it's fixable
Like others have pointed out, since you can get into Download mode fine flash the Stock Odin tar file found here
When you boot up I would consider doing a data wipe (Factory Reset option in Settings>Back up and reset) but that's up to you
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
Ya Ive seen some build.prop changes mess things up. Luckily you could get back up.
Fun feeling huh! lol
fergie716 said:
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
DroidGnome said:
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
Click to expand...
Click to collapse
Glad to hear you're up and running again!!
Best excuse ever to Sprint is when I woke up it was like that haha
Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Another Update:
I just re-flashed with odin, this time it says it successfully completed but once again it's stuck at the flashing Samsung logo with the indicator led on.... I am starting to really freak out lol. I have another file downloading that is supposedly just stock, no root or anything...
rakhov said:
Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Click to expand...
Click to collapse
Actually have the exact same situation going on right now, I will post if I can find a fix. Downloading an alternate stock build I found now and will let you know how it goes.
Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!
rakhov said:
Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!
Click to expand...
Click to collapse
Thats exactly what Odin is working on loading now, Download had just finished.
avarize said:
Thats exactly what Odin is working on loading now, Download had just finished.
Click to expand...
Click to collapse
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD
rakhov said:
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD
Click to expand...
Click to collapse
I've always noticed the LED being on during boot (or some of the boot) and it was also on when I had a bootloop during cm9 so I don't think it means anything.
Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.
rakhov said:
Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.
Click to expand...
Click to collapse
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
Click to expand...
Click to collapse
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 for reboot options to force it into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.
avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 to force into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.
Click to expand...
Click to collapse
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.
rakhov said:
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.
Click to expand...
Click to collapse
Should have explained a bit better. Yes that toolkit
While it was stuck at samsung screen.
1 For AT&T (Obviously)
20 For reboot options
1 For recovery.
Then wipe data/cache
Then wiped cache (no idea why)
then rebooted.
When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium
That is exelent. I am downloading the toolkit right now and will report back shortly.
Once you got it to boot, did you still have root? I am wondering if you flashing the "stock rom" that I posted, if that had any impact. I have only pushed the root66 file, so I am expecting root when(if XD) I get this thing going again. I appreciate you being more thorough with your instructions, and will report back with my results as soon as I get some
Also, are we loners on this? I am not seeing any other posts about going back to stock/stock rooted from modded roms using odin? I am trying to figure out the best method to go back to stock. I made a nandroid and I am sure that would work, but all of this word about having to flash different kernels and bluetooth/wifi drivers to get stock working properly makes me wonder if just using odin is the easiest method, as it restores everything on the phone (to my knowledge).
crash822 said:
When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
That is great, this may sound a little silly, but how do I boot to recovery? Thanks!
UPDATE:Nvm, google hehe. I just did the factory reset...Things are looking good so far, the haptic lights turned on at least...BOOM! We are good gentlemen. It looks like all it took was the recovery wipe. This is great news! I will try to figure out how to mark this as solved, and you crash822, you get a thanks
NP sir. We all have to start somewhere. Luckily for me I was already planning on doing a full wipe so I backed up everything I wanted to keep from my phone onto my computer before using odin.
I seem to be having the same issue. I've downloaded the toolkit as you guys have suggested. are you guys in download mode on the phone while you use this? it seems to want me to be in debugging mode and i can't get to that. I've tried a factory reset with no luck.
I have downloaded the ROM Classic v0.1.0 Supermagic, placed it on my SD card. I have also unlocked my bootloader and have CWM recovery. I have returned to the bootloader screen, went to recovery mode, and went to select which zip I wanted to flash. I found the classic v0.1.0 file and slected it, which I thought would begin the flash/download. It simply opened and gave me 3 more options for files. data/, system/, and META-INF/
I should probably mention that after getting the classic v0.1.0, i extracted it and put that file on my sd card.
I have an EVO 4G, unlocked but still with the S-ON, although I can still flash files. I really appreciate any help.
Don't extract a rom..and use smelkus recovery its better than that one
Sent from my PC36100 using xda premium
but other than that mistake, it looks like I'm on track? and speed really isn't an issue right now. As new as I am, I simply want it to work.
WeAreGuns said:
but other than that mistake, it looks like I'm on track? and speed really isn't an issue right now. As new as I am, I simply want it to work.
Click to expand...
Click to collapse
+1 on what Ireyes said and also wipe all except sd card 3 times, then flash.
Read the Evo guide in my signature
MIKESTONY said:
+1 on what Ireyes said and also wipe all except sd card 3 times, then flash.
Click to expand...
Click to collapse
this will help I hope. i'm stuck in a boot loop atm. I eventually cose a different ROM, papasmurfs CM9, but i kept the same procedures, all went well until this boot loop. hope this wipe helps.
HipKat said:
Read the Evo guide in my signature
Click to expand...
Click to collapse
Wow. That helps. I followed the rules and read everything I could before attempting anything and searched and read some more. Somehow I missed that thread. Would have saved me a boatload of time and frustration.
WeAreGuns said:
Wow. That helps. I followed the rules and read everything I could before attempting anything and searched and read some more. Somehow I missed that thread. Would have saved me a boatload of time and frustration.
Click to expand...
Click to collapse
Try fully Rooting your evo I had the same problems when I unlocked the boot loader on the og evo for the second time.don't worry you can RUU it and get back to fully stock if you have any problems.
this right here is my pretty boy swag!
So my stock, rooted boot animation was getting boring So, I saw a cool Iron Man JARVIS boot that I wanted on my SM-T800 but it was .ZIP and apparently Samsung only use QMG so I open Rom Tool Box, then went to Rom Extras and then Samsung and select to install Binarys for .ZIP instead of QMG - it rebooted and there was a black screen and just boot sound. I then placed the .zip files and rebooted and it was the same, black screen no image and just sound. So I tried to get my original boot screen back and tried to do the recover QMG option, only TWRP loads does something for 2 seconds I see red failed writing and my Tab reboots to nothing but a black screen and boot sound. I've tried multiple times and it never works. I've pasted my original Samsungboot.qmg back into /system/media (where I took it from) but it still don't work.
As is evident, I'm a complete noob, so really need some help here and I figured one of you good gentlemen would help me. I'll state it again, I'm a noob (or idiot for messing with what I don't know, whatever you want to call it) so some advice or help I can follow would be much appreciated. Thanks guys.
Make sure you set the permissions of the files to the same as the rest in that folder.
Also wipe cache and dalvik in twrp.
Ok done both of those and it's still just a black screen with boot sound on start up.
Thanks for the help so far man, I really appreciate it.
bartleby999 said:
Ok done both of those and it's still just a black screen with boot sound on start up.
Thanks for the help so far man, I really appreciate it.
Click to expand...
Click to collapse
The easiest way to fix is to just reflash the stock rom then reroot.
Aw man. Was hoping to avoid that.
Where would I find the stock ROM?
Is it this that I need Ashyx? http://www.sammobile.com/firmwares/download/49140/T800XXU1BOCC_T800BTU1BOC1_BTU/
UK version of the Galaxy Tab S WiFi model.
bartleby999 said:
Aw man. Was hoping to avoid that.
Click to expand...
Click to collapse
Why, it won't affect your personal data?
Are you UK Region?
I thought it would delete everything? Yes, I'm in the UK.
Thanks for the help man.
Ashyx, I just flash that file with Odin the same way I did when I used your Root tutorial right?
I's still be able to follow the below guide to gain root again, yes?
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-twrp-t800-t3079488
Or could I use TWRP that installed with your guide to install the above file?
You can use Flashfire to install, it will root at the same time or just root afterwards with odin if you have already tripped Knox.
I've never used Flashfire, can't see any guides, would be more confortable with Odin Since I've used it before.
Would I need to install TWRP again? Would like to just follow your whole guife again, not much chance of me messing it up then. Yeah I've already trippes Knox, so not worried about that. Thanks for your help man.
In that case just install with odin and then run cf_autoroot.
Ok I'll do that. Thanks man.
Quick update, to say that it did indeed fix the error, so thanks Ashyx.