I have tried to root my Samsung tablet.I think I made a bunch of mistake in the root process because after that I stuck on the "Samsung- powered by android" screen. Then I wiped all the data. I had downloaded Odin and TWRP before the rooting. Now, it gives a warning "No OS Installed! ". What does it mean? Did I deleted Android? What should I do? I just want to run my tablet. Data does not matter.
derya5 said:
I have tried to root my Samsung tablet.I think I made a bunch of mistake in the root process because after that I stuck on the "Samsung- powered by android" screen. Then I wiped all the data. I had downloaded Odin and TWRP before the rooting. Now, it gives a warning "No OS Installed! ". What does it mean? Did I deleted Android? What should I do? I just want to run my tablet. Data does not matter.
Click to expand...
Click to collapse
try odin the original stock OS... see if that works..
Related
Ok, this is my first post so forgive if this is in the wrong section...
I have a friend's Galaxy Note 2 ATT that was stuck on the Galaxy Note 2 Boot screen, and it wouldn't go any further.
Because I work for Samsung at the Samsung Experience Shop, I tried running it through our smart reflash tool
-----> This didn't work because it would fully download it onto the phone, but when it got to the Android with the thing spinning in its chest, it would stop and ALWAYS freeze halfway.
Next step I tried doing was going through Samsung Kies and downloading the stock OS and load that, but the same Android with the spinning thing in its chest would show up and it would freeze.
Due to this guy being my friend I told him I would try anything to get his phone to work again (root, to custom recovery, to custom rom)
My steps so far:
1. I have successfully rooted my device via ODIN 1.85 by using CF-Auto-Root
2. Afterwards, I loaded on a custom recovery via ODIN 1.85 which now is philz_touch_6.07.9
Here is my problem now, I've tried searching everywhere and I can't really find the answer...
Whenever I try to side load a rom through ADB through Android tools (its in the right directory and everything because it transfers over), I keep getting an error message "E: Error in /tmp/update.zip (status 7) Installation Aborted."
Now before I get that error I get stuff like getprop("ro.product.device")==t0lte" ||getprop("ro.build.product").... etc. and it goes on and on.
So far the ROMs that I have tried were Cyanogenmod 10.1 and the Pacman Rom, and yes, both are for the correct device like the model name/number match up. And now how I said I thought I rooted the device, whenever I try to reboot into recovery via Philztouch, it says at the top Root Access is missing. Root device, and I click yes. When it reboots into recovery and I want to turn the phone off again, it still says Root Access is missing.
I am open for anything really. My friend just wants his phone to work again. and I've literally exhausted all of my ideas as I keep running into the same issue.
What am I doing wrong? and is something like this possible to fix? Or is my friend SOL?
Thanks for all the help. It's much appreciated.
Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.
rangercaptain said:
Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.
Click to expand...
Click to collapse
+1 to this^^^^^
Look here»»» http://forum.xda-developers.com/showthread.php?t=1981198
And why not give him something stock instead of a CM Rom??[emoji37]
Plenty of stock 4.3 Rom's in the development section...
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Good advice ^^^^ for your friend.
Ok, thanks for the direct response. I've downloaded the latest TWRP recovery and when I try to push it through ODIN, I still have PhilZ Touch 6..? Sorry, I feel like I'm skipping something simple...
according to a guide, I have to make sure when I'm pushing a custom recovery through ODIN I have to leave Auto Reboot and F. Reset Time UNCHECKED. I made sure they were, and for some reason after it says PASS and thread successful 1 failed 0. When I disconnect the phone and turn it back on into recovery mode, I still has PhilZ Touch...
Use your recovery to flash TWRP. There's a zip version and an odin version.
Ok, I got stock recovery on there just by redoing the CF-Auto Root package through ODIN.
I figured well I can apply the ROM the adb through the stock recovery...
It was going well until I got this error. The last line before the error stated:
"Veryfying update package..."
Error:
E: failed to verify whole-file signature
E: signature verification failed
is that due to the fact that i'm using stock recovery?
In the mean time since that didn't work I'm going to flash TWRP and hopefully that fixes the issue.
I'm kinda just documenting my steps here in case anyone wants to follow and chime in if i'm doing something wrong.
Thanks for the help guys!
************3AM EDIT*****************
Ok so I managed to get TWRP 2.7 on the device as I needed the ability to adb sideload the update.zip to the phone since I can't boot into the phone's OS whatsoever.
This is the error I'm receiving now:
Checking for MD5 file...
Skipping Md5 check: no MD5 file found.
then it restarts and I'm stuck at the Samsung GALAXY Note II screen... what's my next step..? Find a different ROM?
**********Another Edit**************
It has just come to me, I shouldn't have to adb sideload the update.zip or the custom rom... even though I can't get into the phones OS and can't copy and paste to the root of the device. Can't I just copy and paste it to a micro SD card and mount that, and then apply the update from there? And as far as those errors I had earlier, I'm still not sure why I received them...
Again, thanks for all the help
Adb won't work if USB debugging wasn't enabled.
In TWRP you can disable md5 checking.
And you don't unzip the zip file.
Thanks for the reply. ADB didn't work because, in fact, since I haven't been able to turn the phone on, I know USB debugging isn't turned on.
And as far as having the MD5 check, it is unchecked.
I received a success message. However, when I try to boot the phone it still gets stuck at the Samsung Galaxy Note II screen.
******Edit******
Ok ended up using a different ROM, I think PacMan rom? It seemed to work until it got to extracting system files and then the phone sits for a couple minutes, screen turns black. And when I try to wake the screen, only the back and menu buttons come up...
Another thing, even though I've already rooted my device using CF-Auto-Root, When I reboot my device with TWRP I go to reboot and then recovery. Then it warns me saying no OS bla bla bla, and then it says it notices that my phone isn't rooted? And that SuperSU isn't on the device. It asks to install it by swiping. I swipe it starts to install, phone reboots. When I reboot it again, it still tells me that the phone isn't rooted. And with the phone not being rooted, I'm coming to the conclusion why I'm having trouble trying to flash Roms.. Is this a possibility?
Why are you using ADB? just drop the .zip for the ROM you wish to flash onto a micro SD card, and flash from within the TWRP. Don't try to extract the .zip whatsoever.
Hey Folks, I am using a SM-T210
I downloaded a tool called 'Kingo Root' when reading an Article Here from CNET
I run the tool and followed the instructions and at the end it said 'Device Rooted Successfully' Then restarted my Device.
However It then Got stuck into a boot loader loop. So I followed instructions to put TWRP onto the device
I then thought well why not put a decent firmware on it so I used the (StockKitkatRom_T210(R) V1.7) and Side loaded it the messages appeared and said the flash and kernel were written so I pressed restart.
However my Android is stuck loading into TWRP.
I thought maybe I was just being an idiot so I clicked the 'Advanced' setting and selected 'Factory Reset' and then rebooted and still I got thrown to TWRP.
So I decided fair enough obviously Flashing isnt for me so tried to put Stock Firmware back on and used Odin except it failed at the very end which indicates a NAND RW Error?
So bottom line I'm stuck in TWRP anyone know how to remove it.
Again I am using an SM-T210
Dean_186 said:
Hey Folks, I am using a SM-T210
I downloaded a tool called 'Kingo Root' when reading an Article Here from CNET
I run the tool and followed the instructions and at the end it said 'Device Rooted Successfully' Then restarted my Device.
However It then Got stuck into a boot loader loop. So I followed instructions to put TWRP onto the device
I then thought well why not put a decent firmware on it so I used the (StockKitkatRom_T210(R) V1.7) and Side loaded it the messages appeared and said the flash and kernel were written so I pressed restart.
However my Android is stuck loading into TWRP.
I thought maybe I was just being an idiot so I clicked the 'Advanced' setting and selected 'Factory Reset' and then rebooted and still I got thrown to TWRP.
So I decided fair enough obviously Flashing isnt for me so tried to put Stock Firmware back on and used Odin except it failed at the very end which indicates a NAND RW Error?
So bottom line I'm stuck in TWRP anyone know how to remove it.
Again I am using an SM-T210
Click to expand...
Click to collapse
It seems you need to flash a Stock firmware using ODIN to start freshly.
Please avoid using those Chinese Programs with Original Tablets !
Chinese Programs are designed for Chinese Tablets/Phones
Hope problem is solved by now?
I have a rooted zenfone 2. I checked for an update. Not knowing the risks of updating system while rooted, I installed the update, and now my phone is stuck on the boot animation screen. It is stuck on "Asus In search of incredible" screen with the turning gear. I can access fast boot mode and recovery mode, but can't start the phone. My phone has Android system recovery installed, not ClockworkMod or TWRP. I tried to install a different recovery, but my PC doesn't read the phone. I thought that wiping the data and cache will help, but didn't. Help me. I'm a 15 year old noob. My parents will kill me!! Also, I haven't tried to install any ROM's on it. So that's out of the picture.
And neither adb, not fastboot can detect the phone.
My phone is rooted, but the bootloader is not unlocked. I was going to unlock it, but thought of backing data up first. I was trying to find the backup app, but accidentally tapped on system update app. I thought there wouldn't be any harm in checking for an update... Apparently their was a lot of harm.
I also tried installing twrp recovery, but it gets stuck on "Waiting for device"
I'm in dire need of help.
I just need to find a way to switch USB debugging on...... That'll fix all my problems
thanks in advance.
I have the Z008 model, NOT the Z00A.
mudit99 said:
I have a rooted zenfone 2. I checked for an update. Not knowing the risks of updating system while rooted, I installed the update, and now my phone is stuck on the boot animation screen. It is stuck on "Asus In search of incredible" screen with the turning gear. I can access fast boot mode and recovery mode, but can't start the phone. My phone has Android system recovery installed, not ClockworkMod or TWRP. I tried to install a different recovery, but my PC doesn't read the phone. I thought that wiping the data and cache will help, but didn't. Help me. I'm a 15 year old noob. My parents will kill me!! Also, I haven't tried to install any ROM's on it. So that's out of the picture.
And neither adb, not fastboot can detect the phone.
My phone is rooted, but the bootloader is not unlocked. I was going to unlock it, but thought of backing data up first. I was trying to find the backup app, but accidentally tapped on system update app. I thought there wouldn't be any harm in checking for an update... Apparently their was a lot of harm.
I also tried installing twrp recovery, but it gets stuck on "Waiting for device"
I'm in dire need of help.
I just need to find a way to switch USB debugging on...... That'll fix all my problems
thanks in advance.
I have the Z008 model, NOT the Z00A.
Click to expand...
Click to collapse
Hey there!, have you fixed it yet? I'm having the same problem i'm trying this method wwwdottechmestodotcom/recover-bricked-asus-zenfone-2/
Maybe u need to look at this post
http://forum.xda-developers.com/zenfone2/general/guide-recover-fastboot-bricked-zenfone-t3284337
hope it will help u.
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?
Hi there all, I need your help.
I decided to sell my Note 2 and as I tried to factory reset the phone for the new owner- it lead to bootloop witch I don't know how to get out of.
Basically it's N7105 model, unlocked and rooted. TWRP recovery and CyanogenMod 13. Was working totaly fine.
Before factory reseting I've read that to completely clean the data you should encrypt the phone and that will scramble the data. So I went and did that.
After I went to factory reset ,but it did nothing and just rebooted. Apparently it's some known bug in CM13, it's not working -many people experience it. And also there is no way to decrypt the data.
So now where I've made a mistake: I went to TWRP and saw one backup from the times I've installed TWRP and rom, and without thinking I pressed to restore.
But that backup was made when I've installed TWRP but OS was stock.
So now it goes through TWRP saying unable to mount data partition and then boots (not fully) to original Samsung OS but with an error: "Encryption failed. Unable to complete encryption due to interuption. Perform factory data reset (erasing all your data) before use. After resetting, try encrypting device again".
And one button to reset the device. If I press that it will go through the TWRP again as above. I can charge the phone and I can press Vol buttons.
I tried to connect with pc through ADB but looks like no devices are found. And in my Device Manager threre is an Yellow Exclamation mark on the phone line saying "The device cannot start". So that's the situation. Is there I can try before canceling sale?
Thanks for your help!
Paul
Did you try to flash the phone with a stock ROM in Odin?
Big thanks!
I did and it's all good!
What a wonderful program Odin- who created it?
Do you know if I lost root after flashing it?
Thanks!
Yes, flashing a stock ROM will remove root.
Odin is a Samsung product: https://en.wikipedia.org/wiki/Odin_(firmware_flashing_software)