So I used this guide:
https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/
When I got to step 8, the phone would freeze. Super Sume wasn't doing anything. Then the whole phone would freeze. I looked into what it was supposed to do, and I read that this step was just uninstalling the app due to spyware. I figured "I'll worry about that once I get root. Then I can install a whole new rom, and it won't be there regardless." So I moved onto the next step. I got all the way down to step 10, and the adb wouldn't connect. So, I went to reboot the phone, and it says "root is not available, would you like twrp to root?" or something like that. I said yes. Now the phone is in a boot loop. I don't know if I have root or not. I tried doing a factory reset, by wiping. That didn't work. Still boot looping. I know my device isn't lost, but I don't know what the next steps are to getting it back.
I'm also currently downloading http://www.sammobile.com/firmwares/download/65392/N910VVRU2BPA1_N910VVZW2BPA1_VZW/
this, in case I need to start all over with my phone.
Can anyone help me at least get past the bootloop sequence? It goes samsung galaxy screen, samsung animaltion, verizon red screen, then bootloop.
Did you format you're SD card?
Sent from my SM-N920F using Tapatalk
Lost My Mind said:
So I used this guide:
https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/
When I got to step 8, the phone would freeze. Super Sume wasn't doing anything. Then the whole phone would freeze. I looked into what it was supposed to do, and I read that this step was just uninstalling the app due to spyware. I figured "I'll worry about that once I get root. Then I can install a whole new rom, and it won't be there regardless." So I moved onto the next step. I got all the way down to step 10, and the adb wouldn't connect. So, I went to reboot the phone, and it says "root is not available, would you like twrp to root?" or something like that. I said yes. Now the phone is in a boot loop. I don't know if I have root or not. I tried doing a factory reset, by wiping. That didn't work. Still boot looping. I know my device isn't lost, but I don't know what the next steps are to getting it back.
I'm also currently downloading http://www.sammobile.com/firmwares/download/65392/N910VVRU2BPA1_N910VVZW2BPA1_VZW/
this, in case I need to start all over with my phone.
Can anyone help me at least get past the bootloop sequence? It goes samsung galaxy screen, samsung animaltion, verizon red screen, then bootloop.
Click to expand...
Click to collapse
Did you get it working??
Sent from my SM-N920F using Tapatalk
I did. I followed that guide about 4 times, and each time I had to reflash to stock with odin. As all this was happening, on a second computer I was researching why it was bootlooping. Well, as it turns out, the guide is bad. The reason I was bootlooping is because 5.1.1 has a special security detection that if it detects root, it will bootloop. You need a different kernal, but his guide said to turn the phone back on after root but before flashing the new kernal.
So, eventually I just tried my own way. I got the bootloader unlocked, and then went into twrp, to flash the new kernal and supersu from zip. It worked.
As I type this, I'm backing up my real SD card (I used a smaller temporary one for the root process), because I'm going to format this, and only put my pictures/old apks/music on it. That should clear up 90% of the space. After I have it backed up, formatted, and files moved to the SD card I will be flashing my first rom.
I have chosen http://forum.xda-developers.com/not...rom-dr-ketan-rom-dr-ketan-rom-l16-n5-t3370495
this to be my new Rom
Lost My Mind said:
I did. I followed that guide about 4 times, and each time I had to reflash to stock with odin. As all this was happening, on a second computer I was researching why it was bootlooping. Well, as it turns out, the guide is bad. The reason I was bootlooping is because 5.1.1 has a special security detection that if it detects root, it will bootloop. You need a different kernal, but his guide said to turn the phone back on after root but before flashing the new kernal.
So, eventually I just tried my own way. I got the bootloader unlocked, and then went into twrp, to flash the new kernal and supersu from zip. It worked.
As I type this, I'm backing up my real SD card (I used a smaller temporary one for the root process), because I'm going to format this, and only put my pictures/old apks/music on it. That should clear up 90% of the space. After I have it backed up, formatted, and files moved to the SD card I will be flashing my first rom.
I have chosen http://forum.xda-developers.com/not...rom-dr-ketan-rom-dr-ketan-rom-l16-n5-t3370495
this to be my new Rom
Click to expand...
Click to collapse
Please help! what was your own way and what did you do to get the bootloader unlocked?
Related
I'm having one hell of a time with this tablet. This is pushing a month and I'm still not satisfied with my tablet.
Tonight I finally tracked down what I had hoped was a stock firmware for my tablet. Halfway through the download it timed out and when I went to download it again, the same thing happened.
So I tried to take my tablet that isn't "properly rooted" anymore and use Odin 9, instead of Odin 10, and place kitkat on my device rather than be stuck with Lollipop 5.0.2. All of this because The Sims Freeplay app isn't working and I can't find another soul on the face of the earth who can give me an answer to why this is happening.
Now I'm stuck on the samsung logo. I managed to get it back in download mode and that's where I flashed Lollipop 5.0.2 through Odin 10. I figured that would solve my problem. It didn't, but at least I got TWRP back on my device.
I never recovered anything that came with my tablet. I did not think I'd ever go back to unroot nor did I know how to back it up in the first place. So there's nothing in my recovery I can boot from. So what I did was I came back here and I downloaded the recovery for TWRP. I flashed it from my SD card, it told me it was successful... now what? I've rebooted and my device still loads to the samsung logo...and just stays there. The little confetti animation happens behind the logo, but that's it. It doesn't turn off. It doesn't reset itself.
CAN SOMEONE PLEASE TELL ME WHAT I'M DOING WRONG?!
I've already voided the warranty on this device and I regret almost daily that I decided to root in the first place. I say this only because I think rooted devices are top-notch, but I haven't been having very much luck with them. It took me a week to root. When I finally rooted then my favorite app game stopped working. Then I figured I could flash the stock firmware easily (but it seems like every place I go to find kitkat or even stock lollipop I can't find or I do, but files are corrupt or sites are full of ads).
I can't use my device at all now except click around in TWRP which isn't doing me any good.
I just want my tablet back. I spent 500 dollars on this thing and I haven't had time to even enjoy it. It's only two months old.
Please. Again. Someone HELP me. I want to figure this out and I don't want to accept that I bricked my device because I've watched plenty of videos on youtube and people are stuck with a phone that's resetting and all they do is fix it right there in front of my eyes.
Why can't I fix this? What is it that I'm not doing properly?
geekery15 said:
I'm having one hell of a time with this tablet. This is pushing a month and I'm still not satisfied with my tablet.
Tonight I finally tracked down what I had hoped was a stock firmware for my tablet. Halfway through the download it timed out and when I went to download it again, the same thing happened.
So I tried to take my tablet that isn't "properly rooted" anymore and use Odin 9, instead of Odin 10, and place kitkat on my device rather than be stuck with Lollipop 5.0.2. All of this because The Sims Freeplay app isn't working and I can't find another soul on the face of the earth who can give me an answer to why this is happening.
Now I'm stuck on the samsung logo. I managed to get it back in download mode and that's where I flashed Lollipop 5.0.2 through Odin 10. I figured that would solve my problem. It didn't, but at least I got TWRP back on my device.
I never recovered anything that came with my tablet. I did not think I'd ever go back to unroot nor did I know how to back it up in the first place. So there's nothing in my recovery I can boot from. So what I did was I came back here and I downloaded the recovery for TWRP. I flashed it from my SD card, it told me it was successful... now what? I've rebooted and my device still loads to the samsung logo...and just stays there. The little confetti animation happens behind the logo, but that's it. It doesn't turn off. It doesn't reset itself.
CAN SOMEONE PLEASE TELL ME WHAT I'M DOING WRONG?!
I've already voided the warranty on this device and I regret almost daily that I decided to root in the first place. I say this only because I think rooted devices are top-notch, but I haven't been having very much luck with them. It took me a week to root. When I finally rooted then my favorite app game stopped working. Then I figured I could flash the stock firmware easily (but it seems like every place I go to find kitkat or even stock lollipop I can't find or I do, but files are corrupt or sites are full of ads).
I can't use my device at all now except click around in TWRP which isn't doing me any good.
I just want my tablet back. I spent 500 dollars on this thing and I haven't had time to even enjoy it. It's only two months old.
Please. Again. Someone HELP me. I want to figure this out and I don't want to accept that I bricked my device because I've watched plenty of videos on youtube and people are stuck with a phone that's resetting and all they do is fix it right there in front of my eyes.
Why can't I fix this? What is it that I'm not doing properly?
Click to expand...
Click to collapse
I just skimmed through all this reading, so I may have missed a few things. The thing I didn't see if factory resetting. You need to factory reset in twrp. Just go to wipe and factory reset. Now reboot and wait at least 20 minutes as it does take quite a while to boot.
If doesnt do, transfer a custom stock based ROM for your device (any KK ROM should do) to your SD card. Factory reset in twrp and flash ROM. Now reboot and wait.
Typically, flashing with Odin takes 20 minutes to boot up for the first time. Just be sure you factory reset.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
I just skimmed through all this reading, so I may have missed a few things. The thing I didn't see if factory resetting. You need to factory reset in twrp. Just go to wipe and factory reset. Now reboot and wait at least 20 minutes as it does take quite a while to boot.
If doesnt do, transfer a custom stock based ROM for your device (any KK ROM should do) to your SD card. Factory reset in twrp and flash ROM. Now reboot and wait.
Typically, flashing with Odin takes 20 minutes to boot up for the first time. Just be sure you factory reset.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Ok. I just factory resetted. Then I went to reboot and clicked "system". Now it restarted and brought me back to the same samsung logo... do I wait 20 minutes on that screen?
geekery15 said:
Ok. I just factory resetted. Then I went to reboot and clicked "system". Now it restarted and brought me back to the same samsung logo... do I wait 20 minutes on that screen?
Click to expand...
Click to collapse
Yep.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Yep.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
By any chance does it take longer than 20 minutes?
It's been 28 minutes and I'm still on the Samsung logo.
geekery15 said:
By any chance does it take longer than 20 minutes?
It's been 28 minutes and I'm still on the Samsung logo.
Click to expand...
Click to collapse
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Custom Stock Based Rom? Does that mean I'll push myself further away from a stock firmware? Also... where do I find one and are there instructions for it? I thought roms were firmwares up until like 4 hours ago and I've been reading of roots for a little over a month now.
I see you've got the same tablet. By any chance are you running 5.0.2 lollipop and do you happen to know having a rooted device is the reason why The Sims Freeplay won't get past it's splash screen or if it's the app itself and it's newest update that made it wiggy?
I'll flash whatever at this point, but my main reasons for continuing to mess with my tablet was because of not being able to play the sims on there. Every other game I play works.
geekery15 said:
Custom Stock Based Rom? Does that mean I'll push myself further away from a stock firmware? Also... where do I find one and are there instructions for it? I thought roms were firmwares up until like 4 hours ago and I've been reading of roots for a little over a month now.
I see you've got the same tablet. By any chance are you running 5.0.2 lollipop and do you happen to know having a rooted device is the reason why The Sims Freeplay won't get past it's splash screen or if it's the app itself and it's newest update that made it wiggy?
I'll flash whatever at this point, but my main reasons for continuing to mess with my tablet was because of not being able to play the sims on there. Every other game I play works.
Click to expand...
Click to collapse
The only thing I can suggest is download this to your SD card and flash it in twrp. http://forum.xda-developers.com/showthread.php?p=56345482
The Sims may not work because its uncomptiple with lollipop.
Simply, hit wipe in twrp, hit advanced wipe, and tick system, dalivk and cache. Then go back and install the Cm11 zip and reboot. Hopefully it gets you booting
Sent from my SM-T800 using Tapatalk
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
DUHAsianSKILLZ said:
Yep.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
DUHAsianSKILLZ said:
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
ashyx said:
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
Click to expand...
Click to collapse
I understand that. That is why I clicked unroot in supersu and tried the game app, but it still wouldn't work. On my galaxy note 3 I run 5.0 lollipop and my game works fine. My phone isn't rooted and I never decided to root it and then unroot it.
Is an app smart enough to know when a device has been rooted and if are those that hack their actual game on rooted devices uses cloak or xposed or both to by pass their root?
I rather be unrooted for the sake of the game, but how does one find the stock firmware? Or is it not possible at this point?
Sorry for any confusion.
ashyx said:
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
Click to expand...
Click to collapse
Okay. I installed or flashed ironrom to my tablet from twrp. i followed the directions it told me and I decided to pick the regular rom above the custom one that was close to stock. Then it told me that it was going to reboot; which it did. When it came back it got stuck on the same samsung loading screen so I powered it off, went back into TWRP (because powering off now isn't possible, more like restart) and I went to "Reboot " and then I clicked "power off".
I guess I'll be waiting for 10 to 15 minutes.
I Pray I did this correctly.
geekery15 said:
Okay. I installed or flashed ironrom to my tablet from twrp. i followed the directions it told me and I decided to pick the regular rom above the custom one that was close to stock. Then it told me that it was going to reboot; which it did. When it came back it got stuck on the same samsung loading screen so I powered it off, went back into TWRP (because powering off now isn't possible, more like restart) and I went to "Reboot " and then I clicked "power off".
I guess I'll be waiting for 10 to 15 minutes.
I Pray I did this correctly.
Click to expand...
Click to collapse
Thanks for all the help! I'm finally back to where I want to be and the ss freeplay seems to be working. I can't thank you both enough.
geekery15 said:
Thanks for all the help! I'm finally back to where I want to be and the ss freeplay seems to be working. I can't thank you both enough.
Click to expand...
Click to collapse
Why did you reboot back into twrp? You should have just let it do its thing after it rebooted.
So for any others that may happen upon this thread.
What was your solution?
ashyx said:
Why did you reboot back into twrp? You should have just let it do its thing after it rebooted.
So for any others that may happen upon this thread.
What was your solution?
Click to expand...
Click to collapse
I did because I thought it had to be shut down before I powered it on and waited. I realized afterwards that you probably meant to just let it sit for 10 to 15 minutes.
Are you asking me my solution or other peoples solution?
geekery15 said:
Are you asking me my solution or other peoples solution?
Click to expand...
Click to collapse
Your solution.
cant reboot after failed encryption
I was trying to encrypt my galaxy tab s, which is rooted and has lollipop 5.0. Afrer reading encryption failed. I tried to reboot in recovery via twrp. My device doesn't reboot, it just acts like its going thru the motions. Only to return to twrp recovery menu. How do I reboot the system clearing the failed encryptions. I am a noob and any suggestions would be much appreciated.
You will have to go into recovery and wipe the data and cache partition then reboot.
It may take a while to boot up after that.
Well I thought my solution was using IronRom... but i'm not too sure now.
I just got back from work and I went to turn on my tablet and it took me to the same loading screen and then after about 5 minutes it tells me that the system can't respond. It asks me to click "ok" or "wait" ... clicking either just turns my tablet off.
Now the screen has dimmed. It's turning on when it wants and sometimes it'll show me the time in the upper right hand corner, but it won't let me do anything because it's a black screen.
What does all of this mean?
I just noticed if I click the "power button" it just flashes my tablet desktop then goes back to black, but it shows me the battery percentage and the time in the upper right hand corner...
smt 800 stuck in logo
SAMSUNG GALAXY TAB S 10.5 WIFI WHAT IT CAN AND CANT DO
i HAD ROOTED AND INSTALLED LOLLIPOP 5.0 WITH SUPER SU AND TWRP RECOVERY.
I THEN TRIED TO ENCRYPT WHICH FAILED.
MY DEVICE SAID TO REBOOT SYSTEM AND THEN TRY TO ENCRYPT AGAIN. AFTER REBOOTING, MY DEVICE IS STUCK WITH (logo screen)THE SAMSUNG TAB S NAME AT THE TOP OF THE SCREEN AND ANDROID ON THE BOTTOM. I then rerooted with cf auto root thru odin. Odin and my tablet went thru the motions. When everything was complete and device should have initialize, but didn't. This part of the process didn't happen.
I am able to go into DOWNLOAD MODE and can get to manual mode, but I seem to have lost recovery. Here is the info.
android system recovery <3e>
kot49h_t800xxu1af8..
the binary reads: samsung official
system status: custom
Do you have any suggestions.
Well, as usual, I've managed to mess things up and here I am again. Somehow, I installed something or other that required rebooting. When I did, I kept getting an error that the systemui was messed up. So I decided to try to flash a custom ROM since it appeared this thing was already FUBAR and that's where the fun began. It WAS running stock 4.4.2. I wiped everything in preparation to flash the stock .tot file. Went to flash a zip from the external sdcard, and it refused telling me it couldn't mount the card! The only hopeful thing is that it powers up, I can get into download/recovery, and it's recognized by the PC through LGFT and ADB.
I can't flash anything, can't push or install through ADB, can't sideload anything. LG flash tools gets to about 38 seconds and then fails. It's like the devices permission were all changed to read only. The device is rooted and has CWM recovery. Is there a way to completely slick this thing (except for recovery - I'd do that too if need be) to reset permissions.
Any/all suggestions gladly accepted.
gjtoth said:
Well, as usual, I've managed to mess things up and here I am again. Somehow, I installed something or other that required rebooting. When I did, I kept getting an error that the systemui was messed up. So I decided to try to flash a custom ROM since it appeared this thing was already FUBAR and that's where the fun began. It WAS running stock 4.4.2. I wiped everything in preparation to flash the stock .tot file. Went to flash a zip from the external sdcard, and it refused telling me it couldn't mount the card! The only hopeful thing is that it powers up, I can get into download/recovery, and it's recognized by the PC through LGFT and ADB.
I can't flash anything, can't push or install through ADB, can't sideload anything. LG flash tools gets to about 38 seconds and then fails. It's like the devices permission were all changed to read only. The device is rooted and has CWM recovery. Is there a way to completely slick this thing (except for recovery - I'd do that too if need be) to reset permissions.
Any/all suggestions gladly accepted.
Click to expand...
Click to collapse
Surprisingly, there was nothing wrong with the phone nor the software nor the PC. After screwing around with this for a couple of days, I had a thought to try a different USB cable. So, I popped it on and, lo & behold, I'm able to flash to stock! Lesson learned: Don't use cheap cables and try changing cables when you're have weird problems like this. :good:
Hi Hope someone can help.
History of what I did.
Im on BPA1
1. Rooted with Kingroot
2. Ran ADB Commands step by step.
3. Booted into Download mode, phone showed Developer
4. Booted into Android phone was fine.
5. Booted back into Download Mode.
6. Flashed TWRP with Odin.
7. Phone went into bootloop would not go past Galaxy note 4 screen.
This went on for an hr so I decided to flash stock BPA1 to try get phone back to original state. It flashed fine in ODIN but its still boot looping and wont go passed Note 4 screen.
Im getting very worried. Can someone help please
gersrt said:
Hi Hope someone can help.
History of what I did.
Im on BPA1
1. Rooted with Kingroot
2. Ran ADB Commands step by step.
3. Booted into Download mode, phone showed Developer
4. Booted into Android phone was fine.
5. Booted back into Download Mode.
6. Flashed TWRP with Odin.
7. Phone went into bootloop would not go past Galaxy note 4 screen.
This went on for an hr so I decided to flash stock BPA1 to try get phone back to original state. It flashed fine in ODIN but its still boot looping and wont go passed Note 4 screen.
Im getting very worried. Can someone help please
Click to expand...
Click to collapse
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
Cheers Mate, I'm sure I've already tried this, I will try again when I get home.
Thanks for your input.
Il let ya know.
felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
First and foremost... THANK YOU!
I've been pulling my hair out for weeks trying to get my phone to boot, but this boot loop has been driving me insane! I've probably flashed 7 different factory ROMs in Odin no less than 5 times each!
And all I had to do was pull my SD card out??
Second:
How did you know that???
Sent from my SM-G900V using XDA-Developers mobile app
Wired4Fun said:
First and foremost... THANK YOU!
I've been pulling my hair out for weeks trying to get my phone to boot, but this boot loop has been driving me insane! I've probably flashed 7 different factory ROMs in Odin no less than 5 times each!
And all I had to do was pull my SD card out??
Second:
How did you know that???
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
It's a common mistake.
Well, thank you again....
Sent from my SM-G900V using XDA-Developers mobile app
Tiny little explanation, When rooting and unlocking your bootloader via ADB, the script wipes your SD card and puts a special code in it to backup your phones original CID. This may be used to unbrick your phone one day. So your NEWLY unlocked phone is using a new CID and your SD card is on the old one. Hence the boot loop. So when reading the OP, I thought the same thing. I didn't seem his say he pulled out his SD card after rooting. Hopefully you guys got it working again.
Lol, Honestly I dint figure it out. I read somewhere in the forums about it. Dont remember exactly who suggested it. But, it worked for me.
Did it work for you?
I have same problem, was on BPA1, unlocked bootloader, flashed twrp, something went wrong had to flash stock again, CPL1 loads up fine but when flashing back to BPA1 runs into bootloop, help.
you rock
felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
you rock mate ... itried this for 2 hrs and all i had to so is take the damn sd out...thanks
Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app
title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.
Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app
Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.
Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk
Hello,
today I accidentally tapped on "Update" (to 7.1.1) on my rooted Nexus 5X... Something you usually shouldn't do, but it was 2am and I was tired and.... Doesn't matter. After this my phone rebooted and almost instantly showed the dead android with the message "No command". And now I'm stuck there. After rebooting I still land there.
Since the error message almost instantly appeared and since I still can boot into TWRP (3.0.2-2), I think the update wasn't installed and I hope to find a way to avoid the factory reset of my phone. Do you have some tips or possible solutions what I should do in this case?
Thank you for your help.
Its odd this happened, when rooted and twrp installed. in my experience, the update will just simply fail and it will boot back up.... in your case, it sounds like something flashed but the phone didnt like it.... All I can think of is if you cant get into twrp, boot into fastboot and flash the factory image from google, you will loose all data though.....
EDIT, RE-READ you post, if you CAN get into TWRP, try flashing a backup... you should have a backup I hope, lol... First rule of root and flashing is make a backup asap....LOL
When I rooted my phone I did a backup. But the problem is, it was several months ago. So I tried the only method I could save all my data. It wasn't safe, I knew this, but no risk no fun.
My solution was: Download the ota update from Google and flash it with TWRP... Voila! My phone boots properly with the new update... But this method is like I mentioned before not safe and can probably cause a boot-loop with an overwritten recovery. I had to flash my recovery again, but everything works fine now.