Hi,
I sure could use a hand- first day with my Tmobile note 4.
It's a new 910T3. I successfully followed all of Tekhd's instructions on installing root, recovery, etc., and had a phone running on 5.1.1 with root.
I did a dumb thing. Forgot the nandroid backup (doh!) and went to install tekhd's rom without installing cog1 first, and now i don't have a system.
I have recovery, and can get into download mode.... but have no clue what to either odin or flash. the cog1 and dog1 won't install in recovery.
Death by wife is immanent... HELP!
Steve
Edit: update.... panicked too soon, kept digging and digging and found a post from Chr0nicDreamz that saved my butt. Seems like there was a particular version for the t3 that wasn't in the OP and it involved the updater script. *phew*
God bless Chr0nicDreamz.
what version did you use and can you give me the link to where you found it?
Related
Hi guys,
Followed the steps in forum.xda-developers.com/showthread.php?t=736271 to root my N1. All worked ok, and had root access. I proceeded to flash a custom recovery and received an error "mtd: not writing bad block at 0x000xxxxx". I redownloaded the recovery again, with the same issue. I rebooted and found that the recovery had loaded, however, after another reboot, was no longer the Amon recovery, but stock?
Second question is how can i unroot and go back to full stock? Tried a method found in another threat but was receiving a "verification failed" error - i assume because the version being flashed was too old for the FRF91 i had.
Any help is appreciated
Update
Hi ended up downloading EPE76 and renaming it to passimg, and letting recovery find/run it to unroot.
I then upgraded to FRF85B by downloading and renaming it to update.zip and running it from recovery.
And finally, i downloaded FRF91 and renamed to update.zip and ran it, again from recovery console, to get back to where i was before the hassles.
Not sure if this was the correct way to unroot, but my radio, rom version etc all matches before i started the rooting. The recovery flash never stuck (even though i did it in manual mode), and so it seems i am stock again.
Any advice on the issues in my first post?
best way to root
http://forum.xda-developers.com/showthread.php?t=710842
had same issue while rooting my latest nexus one, not exactly sure of how it happend but I just did same process and it worked fine. Command error or adb push into wrong place. I just cut and paste commands and it worked out fine.
First nexus one I unlocked bootloader and ended up selling it, thinking of switching to iphone 4, but decided to stay with n1.
Update
Hi there...
The method i used is a copy of that but without the battery mod.
Didn't really think having to trim the battery pack was a great idea...
Update
osugsxr said:
had same issue while rooting my latest nexus one, not exactly sure of how it happend but I just did same process and it worked fine. Command error or adb push into wrong place. I just cut and paste commands and it worked out fine.
First nexus one I unlocked bootloader and ended up selling it, thinking of switching to iphone 4, but decided to stay with n1.
Click to expand...
Click to collapse
Yeah starting to wonder if i should even bother trying again... just not sure if CM will be worth the effort. Was more doing it to check it out, rather than a need.
If i can find out how to unroot properly (i may have done it correctly above), i may give it another go. Just felt my unroot effort was trial and error and not really game to try it again and stuff it completely.
Hi everyone
Thanks for everyone's support before. It gave some confidance.
It doesn't work though. It's starts updating and then reboot with the message "Update failed, try using Kies, or go to Samsung service centre".
I removed root it didn't help. I got CWD flashed. Could that be a problem.
Could I get rid if it just to be able to uodate?
Need some help here. Kies seems dodgy judging by the posts.
Thanks in advance.
You need stock recovery if you want to update the official way.
What do I do
Could you explain to me what to do please. And should I mess with Kies. Or it wouldn't work either?
Or may be I could just flash it with Odin? Do you know where I could get
the latest Honeycomb flashable file? Since I already have CWM. And everything from xda seems to work. I just thought mabe just ODIN that update if I could get it.
Stock recovery means that I would need to get rid of CWM. How could I do it please?
Surprisingly enough I managed to get back to stock recovery. The Guide in this forum is amazing. I was scared stiff since i never done it before. It went well but still the update doesn't work. No root. No CWM. Still stops and reboots.
Anyone any ideas please?
Exactly what are you trying to do? You want the latest stock rom? Yes, you can flash it with Odin, there's a guide for that also.
I think it worked. I flashed a stock recovery with Odin. And then updated with Kies. It went down rather well. I sleepless night and all that stress just to see that I liked HC 3.1 better. Especially the dock bar that I could swipe before. And now I have to hit a stupid mini triangle.
Anyway, learnt quite a lot. Used Odin for for the first time and CWM. Cool.
It crashed already twice. Could it be because of installing too mush stuff too quickly? I'm just too impatient to get it back on the road. Like over a 20 apps at the rate of 2 or 3 at a time. Or is it supposed to be able to take it and sth is wrong with the ROM?
Cheers
Nobody cares probably but I'd just like to thank everybody who replied to
my posts. Everything seems to work now. I think it's better. Ebook in the update rom reads French now. Which is handy. That's life, as far as the fact that I bought Moonreader goes. Google play did a wierd thing that I didn't ask for but It saved me about 5 hours. It just backed up, finaly that feature worked, 95% of my apps and then automaticly reinstalled them after a crash and a factory reset. So now I have to sort out the sleep debt.
Love this forum even more now.
Oh and the Guide is ****ing brilliant.
Okay so..
I have to spend my days serving my time in the finnish army, so I am a bit clueless of the GNote scene from time to time. I ran Midnote LPF (?) ICS for quite some time and then tried to decrease my DPI. Unfortunately, this resulted in a bootloop, and I tried to fix it by factory reset. Whoop-de-doo. I cancelled it mid way though, if I remember correctly.
8 hours later I got my hands on a computer and tried flashing a firmware with pc-odin. Didn't work. Here's where I've gotten so far:
Flashing PIT and CWM based recovery v5.0.2.7
Flashing Kingdroid ICS Via CWM based recovery or AbyssNote causes phone to reboot at "Flashing /system"
Trying to flash stock GB via Odin hangs at "factoryfs.img"
Tried to reflash bootloader, no help.
Currently trying out flashing GB rom via CWM recovery.
I need quick help as I am going to a Battle-excercise for two weeks tomorrow and I'd really appreciate have my GNote working by that time..
Thank you very much in advance
EDIT: I can confirm that the partinioning guide in http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12 IS INDEED an effective guide to un-superbrick. The guide can be very intimidating for beginners, so bear that in mind. I ran into a faulty partition on the UMS folder, and repositioning it did the trick. Then I just rebooted recovery and installed KingDroid 7.0 GB and it opened like a charm.
Big chance you have a superbrick now, sending it to Samsung repair center is the only option. Search for "superbrick" in this forum. You'll find my name also
I had to send in my device and probably get it back on wednesday...with a new mainboard. On my device a recovery always ended at /system and a pc odin reflash always stopped at factoryfs.img
The last option without sending in your device is following a few threads here. Some posters were talking about a possible solution.
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Posibly meaning this.. I am trying to run this through and will post results.
Yep, that's one of the posts. This was way too complicated for me.
I've send my Note to a samsung service center and they repaired it without any costs. I only reset the binary counter to zero and (partly...because of factoryfs.img) flashed a stock rom before sending the device.
Morality said:
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Posibly meaning this.. I am trying to run this through and will post results.
Click to expand...
Click to collapse
Sounds like a superbrick. Unless you are willing to go through the partitioning experience, I recommend sending it back.
joe2316 said:
Sounds like a superbrick. Unless you are willing to go through the partitioning experience, I recommend sending it back.
Click to expand...
Click to collapse
Im not gonna lie, It was a scary as **** experience. Currently trying to install.. well.. anything.
oh
my
GOD
ITS ALIVE OH MY GOD ITS ALIVE...
the guide worked.. But definately not recommended for beginners, as the dos prompt might be quite intimidating. but the thing definately works.
I found a bad partition from UMS and just relocated it a bit. I think I lost 3gb of space (not sure, will check on that), and unfortunately it formats your INTERNAL sdcard, as i backuped my external one.. BUT WHATEVER
JESUS CHRIST IT WORKED. After following the guide, recovery needed to be rebooted and then I just installed Kingdroid 7.0 GB. The only problem that appeared was that the Samsung Logo screen lasted longer than usually when flashing new firmware. Will update OP.
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them. *fixed
Caelrie said:
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them.
Click to expand...
Click to collapse
Easy fix. ODIN flash the stock COD6 software. Then start over again with cf auto root. There is a thread that had all of the files you need in one zip.
Sent from my SM-N910T using XDA Free mobile app
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Caelrie said:
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Click to expand...
Click to collapse
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
absinthesummer said:
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
Click to expand...
Click to collapse
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Caelrie said:
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Click to expand...
Click to collapse
Cool, glad you got it sorted. Yeah as long as you can access download mode you're golden, and a bonus if you can get into recovery as well.
Excellent job actually searching and reading and fixing your problem, far too many people want answers just handed to them, so kudos to you for that.
Just for the future if you need help, try to remember and list all steps you took (even if you don't know where you went wrong) in excruciating detail because it helps us troubleshoot and figure out what the problem is. Without certain pertinent info it could take a lot longer to solve it.
Overall good job, glad you're up & running.
Go to rapture download the rom and load it to sd card. Then follow directions exactly and u will be ok. No loading anything. Fresh start
BAD ASS NOTE 4
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
ElAguila said:
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
Click to expand...
Click to collapse
Technically you shouldn't be flashing just the partial firmware. It sets up a base so that you can flash a lollipop rom in recovery without issues. I'm not sure why someone is recommending just flashing the partial firmware only. I guess they figured it wouldn't cause issues.
Anyway, here is how the partial firmware should be used:
Flash partial firmware in Odin
Flash flashable stock lollipop in recovery.
Set up rom, make a backup.
From here you can restore your old kitkat backups without the problems that some are seeing (those who Odin the full firmware are having problems restoring kitkat backups/flashing kitkat roms without Odining ank4 first). The partial firmware prevents that but it's designed to be flashed right before flashing a lollipop rom.
I hope that helps some of you who are having issues.
Hello I'm not really that good with mobile tech so excuse my noobness but i decided to dive in and try to root my samsung s6. Here is step by step what i've done so far
Following a few tuts after backups i rooted my phone and verified it with root checker.
Next I downloaded a few popular root apps and removed a bunch of bloatware on the phone
Today I decided to try to install a custom ROM for my phone, after finding a suitable one for my model I proceeded with his guide:
http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-0-t3094423
Next I downloaded all the correct files (I'm confident I double checked)
Now I'm not sure if this is where I went wrong but I installed TWRP custom recovery first
Then I proceeded to install modem with Odin and that went fine it passed and phone restarted
But when I go to install bootloader under BL in Odin it just fails, tried 3 times same result
Can anyone suggest another step in troubleshooting this? If it helps I was running stock samsung os never tinkered with the phone before this
Any advice is appreciated and please let me know if there is any more info i can provide
Thanks
EDIT:
Ok so I posted this late last night after trying to figure it out for a while. This morning I left for work to discover I had no mobile capabilities at all. No data, call, text nothing. Last night I was connected to my wifi at home so I guess I didn't notice. This has been obviously brutal with no communication all day. I tried tinkering a bit with it (did a factory reset through TWRP, tried flashing everything through TWRP) and nothing really helped.
Now I'm not really sure how to proceed so any advice would help as I don't want to brick my phone. What I'm planning on doing next that is the only thing that makes sense to me (again I have very little experience with phones) is to:
1. Re-flash everything through TWRP
2. Re-flash using stock rom, stock bl, and stock modem using Odin
My questions are is there any particular order I need to do this in and also will I have to re-root the phone again after or will this just be the stock rom but still rooted?
Thanks again literally ANY ideas u can throw out here go a long way as I've opened myself a can of worms