I semi-bricked my Optimus One earlier today, but fixed it via KDZ and the India rom fix..
Re-rooted..
and used Root Uninstaller to remove the Bollywood bloatware like I did before..
only this time, all the apps I uninstalled, are still showing in my installed list, but with the "SD card" icon..
they're NOT on the card, I made sure of that..
but idk where to find them in the filesystem..
they're taking up space that I don't really have, y'know.
how would I go about remedying this?
(I'll post a screenshot later, when the site will let me.)
Deathpunkin said:
I semi-bricked my Optimus One earlier today, but fixed it via KDZ and the India rom fix..
Re-rooted..
and used Root Uninstaller to remove the Bollywood bloatware like I did before..
only this time, all the apps I uninstalled, are still showing in my installed list, but with the "SD card" icon..
they're NOT on the card, I made sure of that..
but idk where to find them in the filesystem..
they're taking up space that I don't really have, y'know.
how would I go about remedying this?
(I'll post a screenshot later, when the site will let me.)
Click to expand...
Click to collapse
It's possible that your root didn't take or the system partition didn't get remounted RW. System Apps reside in /system/app . User apps reside in /data/app .
The root did take, I confirmed that.
and the files are not in those locations..
heres the screenshot of what one looks like in app list..
Deathpunkin said:
The root did take, I confirmed that.
and the files are not in those locations..
heres the screenshot of what one looks like in app list..
Click to expand...
Click to collapse
I'm at a loss then. I've never experienced the issue you are facing. You rebooted after removing those apps? Are you using some kind of *2SD script?
Yup, I rebooted.
no, I'm not using any scripts or anything..
The only thing I have my phone doing that it "shouldn't" is the root.
am I going to have to re-flash it, and try to remove them again?
Also, the apps in question are not in the list when I go through Root Uninstaller again.
I'm guessing there's something better than RU, but I just don't know what it is yet xD
Deathpunkin said:
Yup, I rebooted.
no, I'm not using any scripts or anything..
The only thing I have my phone doing that it "shouldn't" is the root.
am I going to have to re-flash it, and try to remove them again?
Click to expand...
Click to collapse
Possibly as a last resort. Do you have a custom recovery installed? If so, try wiping cache and Dalvik cache and then reboot. The reboot will take a few minutes as Android will need to rebuild the caches.
shinobisoft said:
Possibly as a last resort. Do you have a custom recovery installed? If so, try wiping cache and Dalvik cache and then reboot. The reboot will take a few minutes as Android will need to rebuild the caches.
Click to expand...
Click to collapse
Trying to put CWM recovery on is what got me in this mess..
I'm not going to try to do any modding outside of Root untill I get a new phone..
this is the second time I've tried.
Deathpunkin said:
Trying to put CWM recovery on is what got me in this mess..
I'm not going to try to do any modding outside of Root untill I get a new phone..
this is the second time I've tried.
Click to expand...
Click to collapse
I can understand that. Did you use ROM Manager to try and install recovery? I've written a tool for Windows that can flash recoveries via fastboot and fastboot mode. If you're interested, it's called Android Flash Recovery and a link to it's thread can be found in my signature.
shinobisoft said:
I can understand that. Did you use ROM Manager to try and install recovery? I've written a tool for Windows that can flash recoveries via fastboot and fastboot mode. If you're interested, it's called Android Flash Recovery and a link to it's thread can be found in my signature.
Click to expand...
Click to collapse
Yea, I tried to use ROM Manager...
I have no clue what/how to get to 'fastboot' mode..
and I don't know what BB I'm using.
I've tried to find out but nothing showing in my About Phone helps.
Deathpunkin said:
Yea, I tried to use ROM Manager...
I have no clue what/how to get to 'fastboot' mode..
and I don't know what BB I'm using.
I've tried to find out but nothing showing in my About Phone helps.
Click to expand...
Click to collapse
What version of Android is on your device? 2.2 is Froyo which is old baseband. 2.3 is GingerBread which is new baseband.
Download my tool. Make sure USB Debugging is enabled on the device. Complete instructions are in the download archive. It's up to you tho.
I have used Root Uninstaller for 11/2 years on my Optimus V. The Uninstaller doesn't work that well.
I just use it because it auto saves all downloaded apk's, every version. I have to manually delete any saved versions.
Great when an update to an app is borked, or too slow of a data connection to re-install Titanium Backup after a ROM flash (I go to folder on SD card and move TB apk to root of SD card, then install).
Try using Link2SD
It has worked flawlessly to delete any unwanted pre-installed apps from ROM developers and Google Apps.
Sent from my LG-VM670 using xda premium
shinobisoft said:
What version of Android is on your device? 2.2 is Froyo which is old baseband. 2.3 is GingerBread which is new baseband.
Download my tool. Make sure USB Debugging is enabled on the device. Complete instructions are in the download archive. It's up to you tho.
Click to expand...
Click to collapse
Android 2.3.3
is it 100% that it's new Baseband?
and, I might give it a try later today..
I'll update you when I get a chance.
Deathpunkin said:
Android 2.3.3
is it 100% that it's new Baseband?
and, I might give it a try later today..
I'll update you when I get a chance.
Click to expand...
Click to collapse
Yes. Positive. You can optionally use the method just mentioned by AndieOpie150, or ES File Explorer has and uninstall/backup feature too.
shinobisoft said:
Download my tool. Make sure USB Debugging is enabled on the device. Complete instructions are in the download archive. It's up to you tho.
Click to expand...
Click to collapse
Booted in 'fastboot mode' and it just sits at
"
Fastboot mode started
udc_start()
-- suspend --
"
not detected after fastboot by AFR
it detected before the boot, but "Flash Recovery" was greyed out.
still is greyed out.
Deathpunkin said:
Booted in 'fastboot mode' and it just sits at
"
Fastboot mode started
udc_start()
-- suspend --
"
not detected after fastboot by AFR
it detected before the boot, but "Flash Recovery" was greyed out.
still is greyed out.
Click to expand...
Click to collapse
fastboot is a little weird. Boot device into fastboot mode, but not connected to PC. Then connect to PC after getting into fastboot mode.
I think I've seen something like that before. I think it's when the APK is gone but the cache, dalvik etc for the app is still there.
If you haven't yet done anything hardcore to your phone. EG: Reflashing.
And can still boot into your ROM then you might wanna give Clean Master a go.
It's here:
https://play.google.com/store/apps/details?id=com.cleanmaster.mguard&feature=nav_result#?t=W251bGwsMSwyLDNd
It's got a Residual Files cleaner which might get rid of the files that are causing your problems
shinobisoft said:
fastboot is a little weird. Boot device into fastboot mode, but not connected to PC. Then connect to PC after getting into fastboot mode.
Click to expand...
Click to collapse
So, Fastboot before hooking up the phone, gives me a driver searching Windows update for "Android"... I'm guessing that something is missing, yes?
WidowCranky said:
I think I've seen something like that before. I think it's when the APK is gone but the cache, dalvik etc for the app is still there.
If you haven't yet done anything hardcore to your phone. EG: Reflashing.
And can still boot into your ROM then you might wanna give Clean Master a go.
Click to expand...
Click to collapse
if I've got the room, I'll give that a try.
Deathpunkin said:
if I've got the room, I'll give that a try.
Click to expand...
Click to collapse
Clean Master didn't help at all, "Residual Files" only searched the SD card, even though the apps in question are taking up system space.
Thanks anyway Cranky...
might use that later for future uninstalls though.
Deathpunkin said:
So, Fastboot before hooking up the phone, gives me a driver searching Windows update for "Android"... I'm guessing that something is missing, yes?
Click to expand...
Click to collapse
Yeah, the driver from LG.
Go Here.
Scroll down to Manuals & Download, Software Update tab and then "Install the USB DRIVER"
Just get the driver, don't worry about the LG Mobile Support Tool. That's for updating the stock ROM.
Officially but there are no official updates since GB.
WidowCranky said:
Yeah, the driver from LG.
Go Here.
Scroll down to Manuals & Download, Software Update tab and then "Install the USB DRIVER"
Just get the driver, don't worry about the LG Mobile Support Tool. That's for updating the stock ROM.
Officially but there are no official updates since GB.
Click to expand...
Click to collapse
I have the drivers though..
I put that one in, then the United drivers.. which updated the ones from LG...
when I unplug the phone, Windows gave an error about unable to install ADB Modem or something like that..
Related
Okay, so I have used RSD Lite before with no problem. I need to flash my entire device back to stock before tomorrow, but the program is not reading my phone. Motorola Device Manager is installed, same setup I had last time I had to flash after soft bricking...I can't figure it out. Any help would be very appreciated. Thank you.
Moto Q stock with Arrrghhh's kernel v.0.10
Have you entered AP Fastboot mode? Hold both volume button and power. You'll see bootmenu. And navigate using volume down and select AP Fastboot using volume up.
Sent from my XT897 using Tapatalk 2
No Go in Fastboot AP
huatz84 said:
Have you entered AP Fastboot mode? Hold both volume button and power. You'll see bootmenu. And navigate using volume down and select AP Fastboot using volume up.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, totally know what to do, and what order to do it in, only RSD Lite will not acknowledge my device! Crazy, cause I just flashed stock image ASA 14 about 3 weeks ago, no problems.
Nevermind... hehe
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
Are you in Windows? I find Windows pretty annoying when it comes to certain drivers. You might have a look in Device Manager while your phone is plugged in(maybe check with the phone is fastboot mode too), and see if there are any Moto related drivers that have a yellow exclamation point. If so, perhaps reinstalling Device Manager will fix it? Good luck
yogi2010 said:
Nevermind... hehe
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
Are you in Windows? I find Windows pretty annoying when it comes to certain drivers. You might have a look in Device Manager while your phone is plugged in(maybe check with the phone is fastboot mode too), and see if there are any Moto related drivers that have a yellow exclamation point. If so, perhaps reinstalling Device Manager will fix it? Good luck
Click to expand...
Click to collapse
Tried uninstalling and reinstalling Moto Device Manager 3 times...no. Tried RSD Lite versions 5.7 through 6.1...nothing. Is there an actual driver pack I can install that would have the appropriate drivers?
(I have a dual boot laptop, Ubuntu and Win 7, using Windows)
Moto Q stock with Arrrghhh's kernel v.0.10
galacticservant said:
Tried uninstalling and reinstalling Moto Device Manager 3 times...no. Tried RSD Lite versions 5.7 through 6.1...nothing. Is there an actual driver pack I can install that would have the appropriate drivers?
(I have a dual boot laptop, Ubuntu and Win 7, using Windows)
Moto Q stock with Arrrghhh's kernel v.0.10
Click to expand...
Click to collapse
I do have a driver installer downloaded on my computer, but I don't know if it would help you. I will attach it here just in case.
I had this issue a month back, but Moto Device Manager ended up being the solution for me. I have RSD Lite 6.1.5, and it sill recognizes my device in fastboot mode.
edit: the site wouldn't let upload the files for some reason, so I used Dropbox. here is the driver installer I have, but i'm not sure, it might not have solved the issue for me. also, here is RSD Lite 6.1.5 in case you don't have it and wanna try it:
https://dl.dropboxusercontent.com/u/18474790/USB_Drivers_64_bit_4.6.5.zip
https://dl.dropboxusercontent.com/u/18474790/RSDLite6.1.5.zip
hope you get it working,,, i'm sure you will somehow..
yogi2010 said:
I do have a driver installer downloaded on my computer, but I don't know if it would help you. I will attach it here just in case.
I had this issue a month back, but Moto Device Manager ended up being the solution for me. I have RSD Lite 6.1.5, and it sill recognizes my device in fastboot mode.
edit: the site wouldn't let upload the files for some reason, so I used Dropbox. here is the driver installer I have, but i'm not sure, it might not have solved the issue for me. also, here is RSD Lite 6.1.5 in case you don't have it and wanna try it:
https://dl.dropboxusercontent.com/u/18474790/USB_Drivers_64_bit_4.6.5.zip
https://dl.dropboxusercontent.com/u/18474790/RSDLite6.1.5.zip
hope you get it working,,, i'm sure you will somehow..
Click to expand...
Click to collapse
Yeah, I'm sure somehow that I will...thanks for the files, I'll try that now. Oh, by the way, you should check out the Dev Host site (google it), they provide free file uploading and sharing for, well, developers (or anyone for that matter). Only 500 MBs worth of storage is provided for free, but that really is all I need. Anyway, I'll try your advice and let ya know.
***by the way, I need drivers for 32 bit, not 64***
Moto Q stock with Arrrghhh's kernel v.0.10
yogi2010 said:
I do have a driver installer downloaded on my computer, but I don't know if it would help you. I will attach it here just in case.
I had this issue a month back, but Moto Device Manager ended up being the solution for me. I have RSD Lite 6.1.5, and it sill recognizes my device in fastboot mode.
edit: the site wouldn't let upload the files for some reason, so I used Dropbox. here is the driver installer I have, but i'm not sure, it might not have solved the issue for me. also, here is RSD Lite 6.1.5 in case you don't have it and wanna try it:
https://dl.dropboxusercontent.com/u/18474790/USB_Drivers_64_bit_4.6.5.zip
https://dl.dropboxusercontent.com/u/18474790/RSDLite6.1.5.zip
hope you get it working,,, i'm sure you will somehow..
Click to expand...
Click to collapse
No dice, RSD still not reading device...no freaking clue
galacticservant said:
No dice, RSD still not reading device...no freaking clue
Click to expand...
Click to collapse
damn, that sucks! did you ever check Device Manager in the Control Panel. i remember seeing a missing Moto driver there, but then again, that led me on a driver search, which led me to Moto Device Manager. did you completely uninstall it first before reinstalling it?
i dunno, just throwing out ideas here lol. otherwise, you might be able to just fastboot flash the necessary components from the FXZ file to get your setup back to stock. or else use a stock TWRP backup, then reflash stock recovery. hope you get it
yogi2010 said:
damn, that sucks! did you ever check Device Manager in the Control Panel. i remember seeing a missing Moto driver there, but then again, that led me on a driver search, which led me to Moto Device Manager. did you completely uninstall it first before reinstalling it?
i dunno, just throwing out ideas here lol. otherwise, you might be able to just fastboot flash the necessary components from the FXZ file to get your setup back to stock. or else use a stock TWRP backup, then reflash stock recovery. hope you get it
Click to expand...
Click to collapse
Yup, used moto-fastboot.exe to push files FZB fles to device. All was okay until trying to flash system.img.ext4. Had error message. My battery was okay though, but said there was problem with multiflash...any ideas
Sent from my SPH-M930 using xda app-developers app
Try another SD-Card, I had problems with my 32GB Samsung SD-Card.
Loader009 said:
Try another SD-Card, I had problems with my 32GB Samsung SD-Card.
Click to expand...
Click to collapse
RSD Lite will have a hard time reading device due to a SD card?
Sent from my SPH-M930 using xda app-developers app
Sorry, I was thinking about nandroid and TWRP, not of RSD Lite...
My mistake.
Entering AP Fastboot
huatz84 said:
Have you entered AP Fastboot mode? Hold both volume button and power. You'll see bootmenu. And navigate using volume down and select AP Fastboot using volume up.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
You can also hold power and the camera button to enter bootloader, then choose AP Fastboot (just saying for users who may not know).
Loader009 said:
Sorry, I was thinking about nandroid and TWRP, not of RSD Lite...
My mistake.
Click to expand...
Click to collapse
Yeah, I have no problem using TWRP or flashing stuff from Internal or External SD
yogi2010 said:
damn, that sucks! did you ever check Device Manager in the Control Panel. i remember seeing a missing Moto driver there, but then again, that led me on a driver search, which led me to Moto Device Manager. did you completely uninstall it first before reinstalling it?
i dunno, just throwing out ideas here lol. otherwise, you might be able to just fastboot flash the necessary components from the FXZ file to get your setup back to stock. or else use a stock TWRP backup, then reflash stock recovery. hope you get it
Click to expand...
Click to collapse
Okay, now this is weird! I have my system back up and running, but I can only load it by starting the bootloader and choosing "normal startup"; otherwise my device boots into fastboot automatically every time I power down. Seems like I can't utilize stock recovery either when I flash it (otherwise I am using TWRP). My entire purpose behind unrooting and going back to stock was to update to JB as I participated in Moto's soak test. I am still stumped...?
System Up, Stock Recovery Down
Guess I'll try re-flashing the bootloader? or a version from a different/newer image?
galacticservant said:
Okay, now this is weird! I have my system back up and running, but I can only load it by starting the bootloader and choosing "normal startup"; otherwise my device boots into fastboot automatically every time I power down. Seems like I can't utilize stock recovery either when I flash it (otherwise I am using TWRP). My entire purpose behind unrooting and going back to stock was to update to JB as I participated in Moto's soak test. I am still stumped...?
System Up, Stock Recovery Down
Guess I'll try re-flashing the bootloader? or a version from a different/newer image?
Click to expand...
Click to collapse
hmm ok, that's good you made some progress, not sure what's up there. which file did you restore with RSD? i tried restoring the asa14 one last night and got an error immediately, but i'm not sure if i edited the xml properly.
so what i ended up doing was restoring this one: http://forum.xda-developers.com/showpost.php?p=33942232&postcount=12. it will restore everything to the original factory firmware that came with the phone.... except for the system. but i had already restored the stock system with a TWRP backup posted by rangerbry, so it was ok. then i had to run the 2 OTA updates on the phone to get up to the most recent official release. it's a bit convoluted, but it's an option, hehe.
yogi2010 said:
hmm ok, that's good you made some progress, not sure what's up there. which file did you restore with RSD? i tried restoring the asa14 one last night and got an error immediately, but i'm not sure if i edited the xml properly.
so what i ended up doing was restoring this one: http://forum.xda-developers.com/showpost.php?p=33942232&postcount=12. it will restore everything to the original factory firmware that came with the phone.... except for the system. but i had already restored the stock system with a TWRP backup posted by rangerbry, so it was ok. then i had to run the 2 OTA updates on the phone to get up to the most recent official release. it's a bit convoluted, but it's an option, hehe.
Click to expand...
Click to collapse
I think the problem is with the cdrom...my phone keeps booting into AP fastboot automatically like I said...and I was never able to get RSD Lite to recognize my device, so I only used fastboot and TWRP. RSD Lite is sadly not an option for me at this point...
Oh, the image that I previously restored with RSD was odexed and purely stock, ASA 14-15 Sprint. Now it wont read in RSD...
Sent from my XT897 using xda app-developers app
yogi2010 said:
hmm ok, that's good you made some progress, not sure what's up there. which file did you restore with RSD? i tried restoring the asa14 one last night and got an error immediately, but i'm not sure if i edited the xml properly.
so what i ended up doing was restoring this one: http://forum.xda-developers.com/showpost.php?p=33942232&postcount=12. it will restore everything to the original factory firmware that came with the phone.... except for the system. but i had already restored the stock system with a TWRP backup posted by rangerbry, so it was ok. then i had to run the 2 OTA updates on the phone to get up to the most recent official release. it's a bit convoluted, but it's an option, hehe.
Click to expand...
Click to collapse
Something else that I totally overlooked...the red Motorola ripple boot animation doesn't even play anymore! It goes right to the sprint_bootanimation...something's not quite right in Moto Land!
Sent from my XT897 using xda app-developers app
galacticservant said:
Okay, now this is weird! I have my system back up and running, but I can only load it by starting the bootloader and choosing "normal startup"; otherwise my device boots into fastboot automatically every time I power down. Seems like I can't utilize stock recovery either when I flash it (otherwise I am using TWRP). My entire purpose behind unrooting and going back to stock was to update to JB as I participated in Moto's soak test. I am still stumped...?
System Up, Stock Recovery Down
Guess I'll try re-flashing the bootloader? or a version from a different/newer image?
Click to expand...
Click to collapse
Stock recovery still not functioning, but phone doesn't auto load fastboot anymore. Still can only load system from bootloader. But also TWRP doesn't disappear after reboot. I flashed cdrom, but is what is the extension? Is it a .img, or is it supposed to be? In details it just said "file".
Sent from my XT897 using xda app-developers app
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
You've got a few options...forgive me if you've tried any of these already...I'm just offering ideas for you to find one that works for you...
1) restore a nandroid backup if you have one
or
2) ADB sideload a zip for one of the roms in the development sections
or
3) ADB push then flash a zip from the development sections
or
4) Flash the factory images using fastboot
DaMonster said:
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
Click to expand...
Click to collapse
Download this ROM (Odex)
http://forum.xda-developers.com/showthread.php?t=2507861
Boot in TWRP, and either use adb sideload:
./adb sideload path_to_hammerhead_KRT16M_odex_signed.zip
or use adb push
./adb push path_to_hammerhead_KRT16M_odex_signed.zip /data/media/0
Then proceed with flashing it from recovery.
Yep, you have plenty of options so don't panic. Personally, I'd use this as an opportunity to teach yourself how to setup and use ADB and Fastboot commands to flash factory images. Once you teach yourself how to do this properly you will no longer get overly concerned when another situation like this inevitably occurs. This will be a learning experience that you will benefit from later on.
If you are on a Mac, follow THIS GUIDE to properly setup ADB/Fastboot for use. Then use THIS GUIDE to learn how to properly flash a factory image.
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
DaMonster said:
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
Click to expand...
Click to collapse
A few things:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
hotleadsingerguy said:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
Click to expand...
Click to collapse
Good point. I'll reflash to the openrecovery-twrp-xxx version shortly anyway, but the point is valid and I'll make sure to have an official image and regular NANDROID backups handy for future experiments
hotleadsingerguy said:
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
Click to expand...
Click to collapse
None taken. I'm not really young, just new to Android/ tinkering. In any case, blowing $400 on a device is still a big deal and I want to avoid that like a plague Alas, youth has no monopoly on stupid.
zerogun said:
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
Click to expand...
Click to collapse
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
DaMonster said:
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
Click to expand...
Click to collapse
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
J_Dutch said:
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
Click to expand...
Click to collapse
Use "adb push" to copy a zip from your PC to your phone.
The command would be like this:
adb push path/to/zip data/media/0
same issue
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
minerva330 said:
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
Click to expand...
Click to collapse
Just restore a nandroid in twrp
still a noob
jd1639 said:
Just restore a nandroid in twrp
Click to expand...
Click to collapse
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
minerva330 said:
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
Click to expand...
Click to collapse
I wouldn't worry about backing up at this point
still a noob
jd1639 said:
I wouldn't worry about backing up at this point
Click to expand...
Click to collapse
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
minerva330 said:
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
Click to expand...
Click to collapse
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
truly ashamed
jd1639 said:
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
Click to expand...
Click to collapse
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
minerva330 said:
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
Click to expand...
Click to collapse
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
jd1639 said:
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
Click to expand...
Click to collapse
How can I unzip a file from the factory image on my phone if it is on desktop? Am I missing something (thanks for tolerating this)?
At this point I could care less about loosing any apps, data, or pics,
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Maybe if you could give some more detail about what exactly you can and can't get the phone to do, what screens can be accessed, and what you did that lead to this condition, we could offer some advice.
Also, no offence to the devs, but twrp is the devil lol. Most issues I have had in the past have led back to it in one way or another, so I never use it. (Just my opinion)
Tappin G2 Style
I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.
kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
scoobaspeaz said:
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Click to expand...
Click to collapse
Nope, my status us unlocked: 3. But when I get home, I'll try the mfastboot instead if fastboot.
kungpowchicken said:
I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.
Click to expand...
Click to collapse
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
bweN diorD said:
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Click to expand...
Click to collapse
Testing now.
UPDATE: Still no go.
kungpowchicken said:
Testing now.
UPDATE: Still no go.
Click to expand...
Click to collapse
Well that sux.
Your problem is different than what I made this for but I was hoping it would work for you.
What did it do, fail all the way through?
When I tested it on my phone it reported flashing the partitions ok. There was actually extra text displayed while it was doing it that I didn't put into the script, that's how I knew it was working.
Tappin G2 Style
Failed all the way.
kungpowchicken said:
Failed all the way.
Click to expand...
Click to collapse
im running out of suggestions
if you havent tried to put stock recovery back on yet, how about we try that and see what happens.
if you dont know how to do it through adb, just grab the 1.34 utility from the dev forum, it will push it through fastboot.
something is obviously wrong with twrp, maybe we can fix that first.
I tried flashing even the stock Recovery manually and through the 1.34 utility. Always comes up failed. :sad:
Did you try the manual steps that I posted in my links?
i hope that works, but im doubtful.
the utility essentially flashes exactly as you would manually.
he doesnt have a partition issue, im guessing something is wack with the permissions.
if twrp somehow screwed up the permissions to read only, i believe even the partition file cant overwrite it. i could be wrong.
So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.
kungpowchicken said:
So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.
Click to expand...
Click to collapse
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)
penser said:
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)
Click to expand...
Click to collapse
he defiantly has the right fastboot, its in the utility that has been downloaded thousands of times.
if its write protected some how, its not going to flash no matter how you try it.
what i was wondering is if recovery can fix permissions that deep, not sure he said he tried that.
What do you mean with recovery?
kungpowchicken said:
What do you mean with recovery?
Click to expand...
Click to collapse
go into twrp, advanced (i think thats the right section) and look for a line that says "fix permissions" and do it.
Keeps saying it can't mount anything.
kungpowchicken said:
Keeps saying it can't mount anything.
Click to expand...
Click to collapse
thats what i figured would happen
I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
carmike692000 said:
I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
Click to expand...
Click to collapse
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Caseyk621 said:
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Click to expand...
Click to collapse
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
carmike692000 said:
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
Click to expand...
Click to collapse
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Caseyk621 said:
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Click to expand...
Click to collapse
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
EDIT - I'm sure one problem with the computer not listing the phone as a device is it cannot find the device driver to install for it, and I've not been successful googling for it. So in the Windows Device Manager list, my XT1080 has a yellow exclamation mark by it. Also, just installed TiB and froze "Motorola OTA" since I had to wait five minutes to post this edit anyways.
carmike692000 said:
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
Click to expand...
Click to collapse
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Caseyk621 said:
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Click to expand...
Click to collapse
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
carmike692000 said:
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
Click to expand...
Click to collapse
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Caseyk621 said:
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Click to expand...
Click to collapse
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
carmike692000 said:
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
Click to expand...
Click to collapse
Glad I could help! Don't forget to make a backup in TWRP! You may find yourself wanting to go back to stock sooner than you think! I keep trying ROMs but always end up missing active notifications and touch less as well as some others!
Sent From Droid Ultra
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
nubia11 said:
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
Click to expand...
Click to collapse
Flash the stock recovery with fastboot. I forget if you need to also unroot or not. Also make sure you have any apps that were disabled or frozen enabled/defrosted
I have my old Nvidia shield tablet and i have WiFi off and powered off.
I've been reading you can stop the kill switch from i guess changing the boot loader or operating system?
I new to this stuff.
Could someone just give me some directions on how to go threw this process please.
I don't know if it's to late cause i have the most recent update? but like i said it's turned off and WiFi is off and i heard that the kill switch is sent over the internet to your device and you don't have to confirm it.
So i hope my system is safe until i can do what ever you guys advise me to do.
Thank you...
treat your old tablet before connecting the new one to internet
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)
If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.
I used my new tablet and the both were working for the day, both have no problems so far.
I've been reading that they are sending out kill switches in 4 segments, by using the last 2 digits of the serial numbers system.
So mine hasn't gone threw yet i don't think.
So i need to root it?
Then delete the OTA file?
Then flash a custom firmware?
Thanks guys...
Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.
Jarocks said:
If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.
Click to expand...
Click to collapse
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.
Snah001 said:
Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.
Click to expand...
Click to collapse
I see lots of root programs, is there a best one?
Can you flash with TWRP?
And someone said all i have to do is...
"Full Process
1) Unlock Bootloader.
2) Flash TWRP Recovery.
3) Get the no more OTA.zip from XDA and flash it via TWRP
4) Check if the update option is removed from Settings, if not flash it again.
Done! "
Is that ok also?
Thank you...
You need to root to flash twrp?
EowynCarter said:
You need to root to flash twrp?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader to fastboot flash anything.
amartolos said:
No, but you do need an unlocked bootloader to fastboot flash anything.
Click to expand...
Click to collapse
Yeah, that the conclusion i reached.
Flash done, now runing bliss pop. First start got me loads of errors. I went until i realized i had forgotten to wipe. It's been a while since i last played with custom roms.
oliwek said:
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.
Click to expand...
Click to collapse
Well, that's disappointing
oleg77 said:
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)
Click to expand...
Click to collapse
Ok i followed the http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
I got to "On the tablet, select "recovery reboot"
But i didn't see it so i selected reboot, i rebooted and was on stock i think?
1) I can see that a few more steps and i'm rooted.
But i'm nervous to try this again from that point.
Should i just start at unlocking the boot loader?
2) Is rooting the device permanently unlocking the boot loader?
3) can i just no OTA from unlocking the boot loader part?
Ok i got to side loader and in the command it says error can't find device and there's an android guy on his back with a red statement mark.
So I'm in developer USB.
I have unlocked the boot loader
I'm flashing the recovery
And i get to restart in recovery.
Then i get the menus to side load the supersu.zip
I renamed it with out caps, i even made a folder in C:\Program Files\Minimal ADB and Fastboot.
Cause it installed at C:\Program Files (x86)\Minimal ADB and Fastboot.
just to avoid the (x86)
when i try and leave the menu to reset it asked me to root, but i had the error so don't want to brick it if rooting with an error on side loading supersu.zip
What do i do?
Thank you...
says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.
l337g0g0 said:
says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.
Click to expand...
Click to collapse
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I don't have an SD card ATM. LOL
Why is the command with ADB not working?
l337g0g0 said:
I don't have an SD card ATM. LOL
Why is the command with ADB not working?
Click to expand...
Click to collapse
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.
frenziedfemale said:
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.
Click to expand...
Click to collapse
Ok that installed it.
WOW thank for that.
I guess I'm rooted, how do i test it and what does being rooted do for me?
Thank you....
Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok i just flashed nomoreOTA.zip.
It said the file was deleted and was a success.
I guess i can use the internet now?
I'm so nervous to turn the internet on and have the thing reset...
Did i need to run supersu to keep it rooted or always rooted until i use supersu to full unroot.
Thank you...