Before I'm blasted please read this and I'll try explain as best as possible why I am asking for help with a thread that already has been discussed. I rooted my phone and flashed the paranoid ROM and gapps. The link under the paranoid thread was no longer available so I found and downloaded the latest gapps and copied both the ROM and gapps zip to my SD card and then flashed the ROM and then the gapps as directed. Apparently the gapps didn't flash and in rebooted the phone and I'm sure you know what happens when this is done. I have a phone that works but I have no gapps. No SuperSU and no other apps for that matter. I've tried numerois methods to be able to get back into recovery (twrp) to restore my backed up files to no avail. Ive tried getting into download mode, no success, booting into recovery, no success, I've tried to unroot using flashtool DLL and tot but get the error message that lg USB port is blocked when I tried to install the flashtool. I was told to try using flashify which downloaded and installed it but got the message that I don't have root access and no SuperSU privileges and I can't get into recovery that way. Then I downloaded the SDK studio to try and get a cmd prompt but that studio is so big I don't know where to go to open command prompt. All I want to do now is wipe everything off of the phone and go back to the original factory settings. Is my phone a total loss or is there a waynout therlgdlashtool do that? I understand that I may have to find out why I'm getting that message when I try using lgflash tool. Once again, thank you for any input (even a little bashing!) and direction u can give me.
dcm1200 said:
Before I'm blasted please read this and I'll try explain as best as possible why I am asking for help with a thread that already has been discussed. I rooted my phone and flashed the paranoid ROM and gapps. The link under the paranoid thread was no longer available so I found and downloaded the latest gapps and copied both the ROM and gapps zip to my SD card and then flashed the ROM and then the gapps as directed. Apparently the gapps didn't flash and in rebooted the phone and I'm sure you know what happens when this is done. I have a phone that works but I have no gapps. No SuperSU and no other apps for that matter. I've tried numerois methods to be able to get back into recovery (twrp) to restore my backed up files to no avail. Ive tried getting into download mode, no success, booting into recovery, no success, I've tried to unroot using flashtool DLL and tot but get the error message that lg USB port is blocked when I tried to install the flashtool. I was told to try using flashify which downloaded and installed it but got the message that I don't have root access and no SuperSU privileges and I can't get into recovery that way. Then I downloaded the SDK studio to try and get a cmd prompt but that studio is so big I don't know where to go to open command prompt. All I want to do now is wipe everything off of the phone and go back to the original factory settings. Is my phone a total loss or is there a waynout therlgdlashtool do that? I understand that I may have to find out why I'm getting that message when I try using lgflash tool. Once again, thank you for any input (even a little bashing!) and direction u can give me.
Click to expand...
Click to collapse
Just follow my back to stock guide. Everything is there and works perfectly. If your getting that USB port is blocked? That sounds like an issue with your computer and not flash tool
will give it a shot.
OK, I'll try that out and let you know how it goes. Thanks mate. I really appreciate you taking the time to read that rather verbose thread and reply.
Related
Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
HoPi` said:
Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
Click to expand...
Click to collapse
Download a clean copy of Odin and install .
Auto Reboot is normal .
Root and Recovery TWRP
http://forum.xda-developers.com/showthread.php?t=1851548
Root and Recovery CWM
http://forum.xda-developers.com/showthread.php?t=1831173
jje
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet. But since this is getting off topic, I might be better off asking in other threads.
Thanks anyway!
HoPi` said:
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet.
Click to expand...
Click to collapse
Then you are not understanding instructions .
What is your intention .
Root or flash a stock rom .
Root via either method i posted .
Stock rom direct flash tar file via Odin.
ODIN flash is a tar not a zip.
Custom rom via a rooted phone with recovery zip file from ext sd card or sd card .
jje
Come on, the instructions are pretty clear boot in Odin Mode, click a button in Odin, let it restart, finished. The SuperSU zip file is from another guide, where the tar-file didn't include it. So I tried to manually install it via CWM (I think it was 6.0.2.7 or 8), but that didn't work either. Whenever the device reboots, Root Checker Basic runs for a few minutes and says "Sorry, the device does not have proper root access". If it helps, I used this guide:
http://www.android-hilfe.de/root-cu...ly-root-fuer-anfaenger-n8000-n8010-n8020.html
Even though it's in german, the screenshots are pretty obvious.
Sorry never ever seen any method with those sort of instructions.Personally not a clue what they mean .
I have used two methods as posted to root note 4 or 5 times. Rooted standard Samsung phones with cwm and root hundreds of times without any of those instructions.
Even run one standard cwm root via Odin to allow a specific rom install followed by a reroot using TWRP this afternoon .
jje
Sent from my GT-N8010 using xda premium
Thanks to Darkman, I finally got it. The problem was the current firmware update from Samsung. I reflashed with the version from January, followed his tutorial (like I did before - wow, after doing this 3-4 times, it certainly becomes second nature), and BAM, the device is rooted. Thanks anyway JJegan
/I had the touch recovery on there and cyanogenmod 10 I think.. worked fine for a year.
Then I wanted to format and start over, so I did a wipe of everything and now anything I try to flash gives me an error, I can still get into the touch recovery but every rom I've tried won't install, keeps saying error.
I'd like to just throw a rom on it and be done, or go back to stock.
Also, when I try to reboot from the touch flash program it tells me its not rooted and would I like to root it now, swipe to confirm or just exit to deny.
Try to rsdlite/sbf to 100% stock
Sent from my dlx using Tapatalk 4
do what? what does that even mean?
thanks
I hope you have your ROM on your sdcard, if so then "Format Data". You'll lose everything on your internal memory but it should solve your ROM errors, considering your ROM isn't the issue to begin with. Especially if you are trying to go from 4.3 back to 4.2. If it's on your internal storage, then you'll need to do alot more searching on how to use adb and fastboot or hope someone is willing to find it for you and post a link.
You might also what to mention what ROMS / version you are trying to install and what version Xoom you have. If you are trying to install the latest EOS Roms they don't work.
And just as every post mentions before flashing something new... do a Nand backup (backup in recovery).
As for your root issues, it's known for 4.3 and has been mentioned many times on these forums. Do some searches about it here or simply go back to 4.2.
The Xoom is pretty hard to brick.
Domunus said:
I hope you have your ROM on your sdcard, if so then "Format Data". You'll lose everything on your internal memory but it should solve your ROM errors, considering your ROM isn't the issue to begin with. Especially if you are trying to go from 4.3 back to 4.2. If it's on your internal storage, then you'll need to do alot more searching on how to use adb and fastboot or hope someone is willing to find it for you and post a link.
You might also what to mention what ROMS / version you are trying to install and what version Xoom you have. If you are trying to install the latest EOS Roms they don't work.
And just as every post mentions before flashing something new... do a Nand backup (backup in recovery).
As for your root issues, it's known for 4.3 and has been mentioned many times on these forums. Do some searches about it here or simply go back to 4.2.
The Xoom is pretty hard to brick.
Click to expand...
Click to collapse
I have nothing on my SD card or Internal Memory, its completely empty!
Every rom I try to flash gives me an error, I tried a few now and it won't work.
I'm at a loss of what to do
I have Twrp recovery ver 2.5.0.0
I tried to flash later version recoveries but I just get an error
what are trying to flash recovery with? should be using fastboot. with an unlocked bootloader, you, quite literally, CANNOT brick the device
also, ignore the idiot who talked about rsd. that would be beyond stupid.
because you can still get into recovery, you can use adb to sideload the ROM.
adb sideload /path/to/ROM.zip
Sent from my Nexus 5
notbrodie said:
what are trying to flash recovery with? should be using fastboot. with an unlocked bootloader, you, quite literally, CANNOT brick the device
also, ignore the idiot who talked about rsd. that would be beyond stupid.
because you can still get into recovery, you can use adb to sideload the ROM.
adb sideload /path/to/ROM.zip
Sent from my Nexus 5
Click to expand...
Click to collapse
Yes I can get into recovery. Where can I read up on how to use adb again?
I'd love to try that.
THANKS
just download the android SDK and pull adb and fastboot executables ( should be in android-tools). as I use Ubuntu, I don't use the SDK any more.
once you have the adb file, if you place it in the same directory as the ROM, you would just need to 1) open command line 2) CD to directory where the files are 3) in Xoom recovery, go to advanced > sideload 4) on computer, type adb sideload ROM.zip
this is will flash the ROM over. do the same thing for gapps. then reboot Xoom
Sent from my Nexus 5
Yea, problem is, what you're saying, makes no sense to me.
I downloaded android SDK installed the 500 meg program.. Now what
also, it seems I cannot get my computer to recognize my xoom.. I downloaded the drivers and all,comes up unknown usb device.
This just really BLOWS!
I went ahead and did some quick searches for you in google. Hope this helps you, if not, do more searches for ADB Sideload xoom rom. If you don't understand something during one of the steps, google it. BTW, you need to update your TWRP if you plan to mess with 4.3.
If you need a visual guide, go to youtube and type in adb sideload. Good luck.
This is a bit old, but it's simplified and may help you setup ADB.
http://www.xoomforums.com/forum/motorola-xoom-hacking-guides/1838-setting-up-adb-windows-7-64-bit-other-windows-platforms.html
This guide may also help you, it's for HTC but obviously change anything HTC related to Xoom. It shows you how to sideload with every detail.
http://forum.xda-developers.com/showthread.php?t=2317985
ok.. does it matter that no matter what I try no computer can recognize my xoom.. Always says unknown device.. I downloaded moto's drivers and everything.
While in recovery and going to mount it still never recognizes my xoom..
Tried in 2 computers, same results
I've had an LG E970 running the stock ROM for about a year and decided to try out CM. I'm new to this, but I did some research and went ahead and rooted the phone, and then installed ClockworkMod. That went smoothly, so I tried to install CM through CWM and it appeared to work until it finished booting up and led me to the encryption PIN screen. My PIN from the stock ROM won't open it. CWM can't mount the encrypted data partition to wipe it.
I can boot to CWM or the CM encryption screen. I tried doing a restore on CWM but keeping getting MD5 errors. I haven't had any luck finding the stock ROM anywhere online, I tried an LG tool to get the kdz but it kept giving me error messages when I entered the serial number. I used Titanium to backup everything beforehand, but I can't figure out how to use the files to restore the old ROM. I can put files onto the SD card with my computer, but don't know if that'll be any help. I tried using the ADK to connect to the phone in fastboot, but the phone doesn't show up when I enter the fastboot devices command. Will an older version of CM thats based on the same version of Android the phone was encrypted with be able to open the data? I've tried researching this but everything I've found suggests going about it in different ways and nothing I've tried has worked.
If anybody could give me any help I'd appreciate it.
You may wish to refer to [GUIDE][E970]Using LG Flash Tool To Flash .tot Files {Alternate To LGNPST}[WIP]
Of note to you is Post #8 If you still have issues, you can post on that thread as well.
I followed that guide, but got stuck because the LG Flashtool is identifying my phone as a Nexus 4 and not allowing me to install the E970 files. I think the phone ID changed because the CM version I downloaded was converted from the Nexus ROM. I was able to flash an earlier version, but it had the same problem. Do you have any suggestings for a ROM with the correct phone ID? Is there any other ROM that might be able to decrypt the stock Android encrypted data?
Thanks!
I fixed it!
By plugging my SD card into the computer, I was able to add new ROMs to it and flash them in CWM. I was trying out different ROMs, hoping one would show up as the right phone model in LG Flashtool, and I found one for LG Official Kitkat 4.4.2 Stock. It was able to decrypt the data and now my phone is usable again. I'll revert to the stock recovery, wipe the phone (including encryption) and then start over with CM.
Here's a link to the ROM in case anybody else has this problem later:
http://forum.xda-developers.com/showthread.php?t=2771440 - Thread
http://level99.nighthorsemedia.com/geeb/LG-KK-4.4.2-Fixed.zip - Download Link
Thanks!
Ok so thanks ahead of time for any help given, here is my story. I have a E980 with the latest AT&T 4.4.2 on it and should have done a little more reading before I installed a custom recovery. I used a one click rooting app for pc which worked great and root was achieved with no problems. Then not knowing about needing a lokified recovery for this I used FREEGEE and CM Rom Manager to attempt to install a custom recovery which both said they were successful and according to CM Rom manager i am running CM recovery 6.0.3.8. My phone still works fine but I can't factory restore or boot into recovery without getting the secure booting error Cause: boot certification verify. I have looked for the last two days on this form and others trying to find a way to get back into recovery. Everything I have read on this error ends up leading back to me using the recovery to flash another rom or another recovery which I can't do. From what I have read the people with this error normally can't do anything on there phones. I do have Android studio installed (although don't really know how to use it) on my PC in hopes that there is some way I can fix this. Please if anyone can lead me in the right direction so I can get back into a recovery and load the lokified one it would be greatly appreciated.
Thanks again for any help given!
Bump
was rooted on lollipop, tried to update to 2.2 but i think i installed the wifi version (i am an lte owner) tried to put the aosp rom on since i needed to wipe and start fresh anyways. Now i am on the aosp rom which changed my recovery the recovery that loads doesnt mount the sd card (and doesnt see the internal storage). I figure if i can just get back to another recovery i should be able to get back on track.
Scoobydumb said:
was rooted on lollipop, tried to update to 2.2 but i think i installed the wifi version (i am an lte owner) tried to put the aosp rom on since i needed to wipe and start fresh anyways. Now i am on the aosp rom which changed my recovery the recovery that loads doesnt mount the sd card (and doesnt see the internal storage). I figure if i can just get back to another recovery i should be able to get back on track.
Click to expand...
Click to collapse
Are you rooted? if so, with flashify, flash another custom recovery. I'd recommend TWRP 2.8.5.0. Its here, http://forum.xda-developers.com/shield-tablet/development/wip-twrp-2-8-0-1-unofficial-t2877117/ and its on the latest posts as zip attachment (you need to extract the zip, because it contains an *.img).
If not, (I have not tried this because I haven't got the need to do it)
you can flash TWRP 2.8.5.0 via fastboot, but you need to unlock the bootloader.
problem is i dont have gapps installed so unable to use flashify. When i try to use adb to install them i get error closed
then waiting for device.
tablet is showing in device manager as google galaxy nexus adb interface
so i believe drivers are installed correctly.
Scoobydumb said:
problem is i dont have gapps installed so unable to use flashify. When i try to use adb to install them i get error closed
then waiting for device.
tablet is showing in device manager as google galaxy nexus adb interface
so i believe drivers are installed correctly.
Click to expand...
Click to collapse
You could do the second solution. But I have never done it, so I cant help you with that, just with what I theoretically know.