So I've got a bit of a problem. I think it's a quite unique one, tried searching for it, but no results.
First of all, a little backstory. My USB-cable port broke. I usually clean it with a toothpick or so, just to get dust out of it. I've done this with my older phones as well, but never had any casualties. Maybe this was my first misstep, but I have to say that the port was never really perfect since day 1.
Anyway, my USB-port broke a few days ago, which means no charging. Before I ran out of battery life, I really didn't know what to do, because since I rooted it, it has no warranty. So at 3% of battery life, I got desperate, freaked out and wasn't thinking straight and deleted SuperSU from my phone through the app, hoping that if it needed to be fixed by a "professional", I could just send it back. Smart eh?
I ordered a wireless Qi charger to charge my phone and it was delivered today. Works fine, my phone turned on again, but without SuperSU installed. So I went to chainfire's website and downloaded the SuperSU zip from there and flashed it. Bootloop. I did some googling and read that I need the unofficial updated version, since I've got a 6.0.1 ROM. I totally forgot about that, because it has been a while since I flashed the 6.0.1 ROM.
So I've got this problem: I need to get the new version of the SuperSU zip on my phone, but I can't connect to my PC using a USB cable and I can't download it directly on my phone because of the bootloop. And the Nexus 6 doesn't have a SD card slot, of course. Could there be some other way to delete SuperSU, or very maybe to transfer files wirelessly through TWRP?
I already factory resetted it, with no results. Help? Please?
How about you restore a backup.... You have one on the phone right???
You can also navigate twrp via the provided file manager.
Do you have a ROM zip left on the phone? If so wipe and flash it to start fresh.
Wireless adb push?
Sent from my Pixel using XDA-Developers mobile app
Wireless adb doesn't work in recovery.
Ah hmmm... Then it needs to be physically repaired. Can't think of any other way
Sent from my Pixel using XDA-Developers mobile app
khanam said:
Ah hmmm... Then it needs to be physically repaired. Can't think of any other way
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Really no other way than repairing it physically? I've heard that can be quite expensive and I'm getting a new phone in a month or two, so I don't really want to spend a lot of money on a phone which I'm not going to use afterwards anyway.
I tried removing SuperSU manually following the steps on this website, but instead of using ES file explorer, I mounted system and used the file explorer in TWRP. But that didn't work either.
If there isn't any other way, could formatting data help to at least stop the bootloop from happening? I wouldn't really mind doing so, because all of my pictures are saved on google photos and I got a TitaniumBackup of all my userapps from a few weeks back on Google Drive.
IYIatthys said:
Really no other way than repairing it physically? I've heard that can be quite expensive and I'm getting a new phone in a month or two, so I don't really want to spend a lot of money on a phone which I'm not going to use afterwards anyway.
I tried removing SuperSU manually following the steps on this website, but instead of using ES file explorer, I mounted system and used the file explorer in TWRP. But that didn't work either.
If there isn't any other way, could formatting data help to at least stop the bootloop from happening? I wouldn't really mind doing so, because all of my pictures are saved on google photos and I got a TitaniumBackup of all my userapps from a few weeks back on Google Drive.
Click to expand...
Click to collapse
as noted above, you can just do a clean flash of any rom zip you have in your phone. After you boot up, there are a ton of apps in the Store that would let you send files wirelessly. Solid Explorer for example as you can set your phone as an FTP server.
ibsk8 said:
Wireless adb doesn't work in recovery.
Click to expand...
Click to collapse
I thought it was a feature of TWRP or CWM to have wireless adb in revcovery?
qnc said:
I thought it was a feature of TWRP or CWM to have wireless adb in revcovery?
Click to expand...
Click to collapse
cwm doesnt have a nexus 6 recovery made. and thats not a feature of twrp.
jibust said:
as noted above, you can just do a clean flash of any rom zip you have in your phone. After you boot up, there are a ton of apps in the Store that would let you send files wirelessly. Solid Explorer for example as you can set your phone as an FTP server.
Click to expand...
Click to collapse
Exactly what I was going to say, just use a file manager to transfer over the zip (I use x-plore file manager by lonely cat games, which supports FTP/SFTP/SMB and also will start a local webserver to you can use the for manager from your PC.
Related
The micro USB charging port on my wife's D4 just died. I received the warranty replacement from VZW. I need to return the old D4 to stock.
Battery is dead and can't charge via USB. I bought the D4 inductive charge door from VZW, and will buy a powermat to charge it, so charging it should not be a problem.
I did a search on this, and found various threads for dead USB ports, but not a solution for what I need.
QUESTION: How can I unroot, return to stock ROM and recovery, and re-lock the bootloader without USB access? I know there are various apps I can use to transfer files to the device via wifi, but is there a ZIP file I can flash with Clockworkmod Recovery to re-load stock ROM, unroot, re-lock bootloader, and re-load stock recovery?
SoCalNewb said:
The micro USB charging port on my wife's D4 just died. I received the warranty replacement from VZW. I need to return the old D4 to stock.
Battery is dead and can't charge via USB. I bought the D4 inductive charge door from VZW, and will buy a powermat to charge it, so charging it should not be a problem.
I did a search on this, and found various threads for dead USB ports, but not a solution for what I need.
QUESTION: How can I unroot, return to stock ROM and recovery, and re-lock the bootloader without USB access? I know there are various apps I can use to transfer files to the device via wifi, but is there a ZIP file I can flash with Clockworkmod Recovery to re-load stock ROM, unroot, re-lock bootloader, and re-load stock recovery?
Click to expand...
Click to collapse
Assuming you are successful in getting your D4 charged, following these steps SHOULD get you back to a stock unrooted phone without the use of the USB port. Make sure you have backup up anything you don't want to lose before you do this.
1. Go in to safestrap recovery, delete any ROM slots, and boot back into your stock ROM.
2. Open up the safestrap app and select uninstall recovery.
3. Uninstall the safestrap app.
4. While you are still rooted, use a file explorer and delete any incriminating leftover files (nandroid backups, etc.)
5. Install and run Ginger Unroot from the Play Store (Full disclosure: I have never actually used this app). Costs 99 cents.
6. After Ginger Unroot does it's thing, check to make sure Superuser is not longer installed on the phone.
7. Boot in to stock recovery and perform a factory reset.
Honestly, I would probably just skip step 6 and manually delete superuser. It's pretty unlikely they will really be looking to see if you rooted it since you're returning it for a hardware issue. Also, according to another thread on XDA, rooting the D4 triggers some sort of check that cannot be undone. If true, unrooting your phone won't help.
Good luck!
kwyrt said:
It's pretty unlikely they will really be looking to see if you rooted it since you're returning it for a hardware issue.
Good luck!
Click to expand...
Click to collapse
Do you really think so? As since ics I have not rooted my for as I have bad luck with the ear piece speaker in my past d4...
Sent from my DROID4 using xda app-developers app
dbreezy187 said:
Do you really think so? As since ics I have not rooted my for as I have bad luck with the ear piece speaker in my past d4...
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Just my personal opinion so take it for what it's worth. I've never actually had to return a phone myself. But, I have yet to hear of someone being turned down for a warranty repair/return because their phone was rooted. And I do know someone personally that returned their D4 under warranty for a faulty screen that was rooted and running a custom ROM and they never said a thing. I'm guessing the only reason they would look into it being rooted was if you soft bricked it, wouldn't boot, something like that where they suspect it was something you did to cause it.
Sent from my D4 - AOKP
kwyrt said:
Assuming you are successful in getting your D4 charged, following these steps SHOULD get you back to a stock unrooted phone without the use of the USB port. Make sure you have backup up anything you don't want to lose before you do this.
1. Go in to safestrap recovery, delete any ROM slots, and boot back into your stock ROM.
2. Open up the safestrap app and select uninstall recovery.
3. Uninstall the safestrap app.
4. While you are still rooted, use a file explorer and delete any incriminating leftover files (nandroid backups, etc.)
5. Install and run Ginger Unroot from the Play Store (Full disclosure: I have never actually used this app). Costs 99 cents.
6. After Ginger Unroot does it's thing, check to make sure Superuser is not longer installed on the phone.
7. Boot in to stock recovery and perform a factory reset.
Honestly, I would probably just skip step 6 and manually delete superuser. It's pretty unlikely they will really be looking to see if you rooted it since you're returning it for a hardware issue. Also, according to another thread on XDA, rooting the D4 triggers some sort of check that cannot be undone. If true, unrooting your phone won't help.
Good luck!
Click to expand...
Click to collapse
kwyrt - THANK YOU for your help! I am heading out later today to get a charging mat to use with the inductive charger, then I will try the steps you outlined above.:laugh:
Yes thank you putting it that way I may finally get mine rooted again...
Sent from my DROID4 using xda app-developers app
Update: I have not been able to test the above directions yet because no local stores seem to carry the inductive charging mat (I've tried Verizon Wireless, Sprint, Radio Shack, and Best Buy).
I will buy the charging mat online, then update thread with outcome once it arrives.
Update 2: the PowerMat that I ordered on Amazon arrived today. Unfortunately it is not compatible with the Droid 4 inductive charging case (Droid 4 requires QI, PowerMat is not QI).
I ordered a QI charging mat, and it arrives Monday. I'll report progress then.
kwyrt said:
Assuming you are successful in getting your D4 charged, following these steps SHOULD get you back to a stock unrooted phone without the use of the USB port. Make sure you have backup up anything you don't want to lose before you do this.
1. Go in to safestrap recovery, delete any ROM slots, and boot back into your stock ROM.
2. Open up the safestrap app and select uninstall recovery.
3. Uninstall the safestrap app.
4. While you are still rooted, use a file explorer and delete any incriminating leftover files (nandroid backups, etc.)
5. Install and run Ginger Unroot from the Play Store (Full disclosure: I have never actually used this app). Costs 99 cents.
6. After Ginger Unroot does it's thing, check to make sure Superuser is not longer installed on the phone.
7. Boot in to stock recovery and perform a factory reset.
Honestly, I would probably just skip step 6 and manually delete superuser. It's pretty unlikely they will really be looking to see if you rooted it since you're returning it for a hardware issue. Also, according to another thread on XDA, rooting the D4 triggers some sort of check that cannot be undone. If true, unrooting your phone won't help.
Good luck!
Click to expand...
Click to collapse
So the inductive charger arrived last Monday. It worked! Device is all charged up despite the non-functional USB port.
Rooted device when it was on GB, then the OTA update brought it to ICS (which removed root).
Here's where I'm at:
- no root (but superuser still installed, and can't be removed)
- stock recovery
- broken USB port
Here's what I've tried:
- Ginger Unroot did not work
- Can't remove superuser from Google Play
- Can't remove superuser from settings/apps
- Can't remove superuser with Root Explorer (no longer have root, so I can't acquire root privileges)
- Can't remove superuser with Titanium Backup (no longer have root, so I can't acquire root privileges)
Given lack of USB, and lack of root, any ideas how I can remove Superuser and restore to stock?
SoCalNewb said:
So the inductive charger arrived last Monday. It worked! Device is all charged up despite the non-functional USB port.
Rooted device when it was on GB, then the OTA update brought it to ICS (which removed root).
Here's where I'm at:
- no root (but superuser still installed, and can't be removed)
- stock recovery
- broken USB port
Here's what I've tried:
- Ginger Unroot did not work
- Can't remove superuser from Google Play
- Can't remove superuser from settings/apps
- Can't remove superuser with Root Explorer (no longer have root, so I can't acquire root privileges)
- Can't remove superuser with Titanium Backup (no longer have root, so I can't acquire root privileges)
Given lack of USB, and lack of root, any ideas how I can remove Superuser and restore to stock?
Click to expand...
Click to collapse
Like previously stated, its prolly going to get tossed into a refurb bin where it will under go fresh flash of firmware after some little asian will replace the speaker and usb port. I wouldnt stress it.
wheeliest said:
Like previously stated, its prolly going to get tossed into a refurb bin where it will under go fresh flash of firmware after some little asian will replace the speaker and usb port. I wouldnt stress it.
Click to expand...
Click to collapse
Gotcha. I just want to avoid getting charged the $300 because they see it was rooted. Would be lame since the device's mechanical USB port failure was completely unrelated to the device being rooted.
Has anyone returned a device to VZW that is still rooted? Did they charge you the $299?
I need help please
PLEASE...... I FLASHED MY LG-E739 wit MIUI V4 rom,
Den i decided to run a font.....when i reboot for de font to take effect it refuse to boot..stopped at de miui logo and have
tried everything to gain recovery mode but none seems to be working...
Please if anybody can render help to me i'd be very greatful.
Hi all.. Firstly, so sorry about the generic title.. but as you will see, i have quite a few questions and I wasn't sure what to put.. or even if this needs to be in a different section.. sorry mods..
Anyway, here we go.. (advanced warning.. im not a complete idiot.. but not far off. so go gently)
HTC one sim free from phones4u in the UK.
im on android 4.1.2
software 1.28.401.7
htc sdk api level 5.12
The story so far:
Ive rooted my HTC one as I need to have rSAP working on it for my car (Audi). Also, I found the stock bluetooth stack didn't seem to work with my car either so i installed bluetooth phonebook app v 1.1.4.. this all seems to work well. I used rSAP v2.3.2
Now, I carried out all the above myself with lots of reading and to be perfectly honest, lots of trial and error installing it all. I didn't find it easy and for the life of me, I can't remember the steps.
The issue i have:
1. I keep getting a notification for an OTA update for my phone. I have tried to run it once.. but it did not install. I'm assuming because my phone is rooted. I force stop it, but it comes back every time i reboot.
2. I've noticed any app that requires root access is failing. (not all the time, some of the time) and if I go into SU it tells me the binary files need to be updated. I have two options. Run "normal" or "TWRP/CWM" neither of them work.
If i pick normal. It says installing, then reboots and is basically the same. The other option boots me into the recovery but I can't see any update to be applied.
UPDATE: I have now resolved this. I simply downloaded the latest zip file for SU.. booted into recovery and ran the zip update from there and it worked..
Now, you super clever lot probably think this is fun to mess around with.. but us, dare i say it, older peeps just really want to be able to press a button and it works.. (i know iphone.. but give me some credibility).
What I'd like to achieve:
1. I've ordered an OTG cable and drive today (be here tomorrow) with a view of taking an off device back up of my current data / app setiings etc. I assume this is easy to do?
2. I'd like to unroot and update the phone to the latest updates via the OTA service
3. I'd really like to get the rSAP/Bluetooth working with very little fuss
4. Put all my email accounts data etc back to where it was.
How to do achieve my request:
Over to you guys... just please for my own sanity.. and anyone else that reads this in the future.. make it easy.. just remember.. I'm not R2D2...:laugh:
Thanks so much.......... i will personally thank each and every useful reply..
If you're rooted, I'm guessing you're using a custom recovery? The OTA won't install if you have a custom recovery installed.
1. Yes, no issues there, but unrooted devices can only r/rw on FAT32 devices, and if your drive is NTFS, you need an app that requires root.
2. No need to unroot for OTA
3. Not too sure about this one
4. OTA won't wipe anything unless it specifically says so.
ArmedandDangerous said:
If you're rooted, I'm guessing you're using a custom recovery? The OTA won't install if you have a custom recovery installed.
Click to expand...
Click to collapse
Yes correct, I have the TWRP, I believe.
1. Yes, no issues there, but unrooted devices can only r/rw on FAT32 devices, and if your drive is NTFS, you need an app that requires root.
Click to expand...
Click to collapse
OK.. so I should be good to go with NTFS format drive. Is this as simple as I think, i.e. plug in the OTG cable and drive and go into the recovery and backup from there?
2. No need to unroot for OTA
Click to expand...
Click to collapse
I'm a bit confused with this reply, as I don't seem to be able to complete the OTA update becasue I have custom recovery.. Do I need to remove custom recovery then apply the OTA update? If you could just expand on this please? i.e if i need to remove custom recovery, how do i do it?
Thanks
uktivo said:
Yes correct, I have the TWRP, I believe.
OK.. so I should be good to go with NTFS format drive. Is this as simple as I think, i.e. plug in the OTG cable and drive and go into the recovery and backup from there?
I'm a bit confused with this reply, as I don't seem to be able to complete the OTA update becasue I have custom recovery.. Do I need to remove custom recovery then apply the OTA update? If you could just expand on this please? i.e if i need to remove custom recovery, how do i do it?
Thanks
Click to expand...
Click to collapse
Hey,
Because you are rooted, you will not be able to install otas. They may notify you they exist, but you can't install them.
How do you get rid of them?
Well you're on a stock Rom. That Rom will receive otas from your service provider. You can install a custom Rom. It's fun! it gets rid of the notification but that's only like 2% of any advantage you can have from a custom Rom. Plus that ota that's trying to come to your phone is most likely already on a custom Rom, as the devs get leaks and port them way before regular users receive them. You could give it s try?
No idea about the first post.. loving the Audi part though haha!
Sent from my HTC One
ArmedandDangerous said:
How do you get rid of them?
Click to expand...
Click to collapse
Pull down the banner from the top of the phone. Click and hold the notification for the update, click app, then pick to force close it. It then goes away until you next re-boot.
uktivo said:
Pull down the banner from the top of the phone. Click and hold the notification for the update, click app, then pick to force close it. It then goes away until you next re-boot.
Click to expand...
Click to collapse
Think you're quoting the wrong person
As I said in my earlier post, you can still receive OTAs and apply them even if you are rooted. The part that makes it fail is the custom recovery. You should be able to find the correct stock recovery from one of the threads here on XDA, or if you have ever received an OTA before on your device, the OTA zip file should still be in your internal SD.
Flash the stock recovery over TWRP (make sure to do a nandroid/backup first) and apply the OTA. You will probably lose root, but just root it again the usual way.
Then you can flash a custom recovery, root, etc etc all over again.
About the USB OTG, I believe TWRP always saves the nandroid backups internally, but you can always transfer them off to a USB device through USB OTG if you want. I don't think it natively supports reading from USB OTG while in recovery.
Why have it so complicating?
Hi,
what I don't understand is why your Audi is not recognising your phone properly? I stream music at home via BT to an APT-X receiver plugged into my stereo, and using quite often rental cars of all makes, I simply connect it, punch the PIN into my fone and the One phonebook is available.
Now, as you are already rooted, and of course unlocked, just download and flash a Custom ROM. They are rooted, and some are based on 4.2.2 and work very well.
No need to fuss about with what you are about to do!
Don't forget to backup imortant stuff you want to keep on your SD card, simply copy it over to your computer for future reference. JB 4.2.2 is organising the SD card structure differently, so you copy stuff back to SDcard/0/
Custom ROMs are featuring the latest updates anyway very quickly, so there really is no need whatsoever to wait for an OTA (which you should never ever attempt to flash when rooted/S-off-ed)
Looking forward to see what you are telling me about the Audi BT connection trouble. I never had any!
Audi..bless them, use a strange protocol. The stock Bluetooth stack will connect but will not transfer the contact information. It can be fixed once root is gained. In all honesty Audi really need to look at this problem. My car is an A7 about 5 months old now but I think they may have addressed it on the latest builds..If course, I won't get the upgrade for free will I...
Sent from my HTC One using Tapatalk 4 Beta
uktivo said:
Audi..bless them, use a strange protocol. The stock Bluetooth stack will connect but will not transfer the contact information. It can be fixed once root is gained. In all honesty Audi really need to look at this problem. My car is an A7 about 5 months old now but I think they may have addressed it on the latest builds..of course, I won't get the upgrade for free will I...
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Sent from my HTC One using Tapatalk 4 Beta
uktivo said:
Audi..bless them, use a strange protocol. The stock Bluetooth stack will connect but will not transfer the contact information. It can be fixed once root is gained. In all honesty Audi really need to look at this problem. My car is an A7 about 5 months old now but I think they may have addressed it on the latest builds..If course, I won't get the upgrade for free will I...
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah, to much Iphones stuff around! hehehe
Try maybe with the Custom ROM in my signature. It worked very well with the Ford Kuga I had last week, music as well as contacts.
Just read up a bit on the different SD card managment google implemented with the multi user stuff.
And I have to say: Audi A7 ???? Nice motor!
Yes , it's a lovely car.. Thanks.. Also; thanks for the info. I will investigate roms..
Sent from my HTC One using Tapatalk 4 Beta
Hi all, Sorry I've been away working for the last few weeks so I've not had chance to do any of the above.
I was hoping I could get some easy to follow (trust me, it has to be easy at my age) instructions on the best way to achieve what I want to do. If the step by step instructions could include links ot the downloads i need, that would be fantastic.
Re-cap on what I want to acheive:
My phone right now:
The phone was purchased from Phoes4u (UK) as a sim free unit. I currently have an O2 sim inserted
Android 4.1.2, HTC sense 5, Software 1.28.401.7
HTC SDK API level 5.12
Kernel 3.4.10-gddcfb8croot
When i boot into recovery it tells me:
M7-UL PVT SHIP S_ON RH
HBOOT-1.44.0000
I have added rSAP v2.3.3 to the phone in order for my car to have access. http://www.android-rsap.com/compatibility.html
I have one exchange email, some movies, and basically thats it.
----------------------------------------------------------------------------------------------------------------------------------
I would like to update to the latest Jelly Bean and ensure I keep rSAP for my car. If there is a way to back up all my data and movies and simply press a button to re-install it, data, settings for email etc that would be fantastic.
Please help if you can.....
thanks.
To start I broke my holster this morning. So I put my phone in my pocket like everyone would do. I apparently didn't lock the phone first. (This of course being just after I rooted and installed some Root features such as Titanium Backup) This led to only God knows, my phone opening many apps including TiB and settings. Somehow google account syncing stopped working. I read some suggestions and tried them all including a factory reset. After the reset nothing changed now except I had a phone that had no contacts or anything else tied to google. I retried editing the hosts file in /etc. I cannot edit it with Root Browser, Root Explorer, or even after using another program called mount r/w r/o. I did another stupid thing by deleting the host file in an attempt to replace it with another I created. Only good news is now the google account will get past the screen that says i don't have a reliable connection to the server. Still cannot access the play store but I do now have calendar, contacts, and a few other things. Any ideas how I could write to /etc
Sincerely,
My stupid self.
P.S.
I already ordered another holster.
EDIT: I factory reset once more and play store started working. I did root again and the host file is still deleted.
If you're not worried about your apps and data, you could always ODIN back to stock and start over. It may not be the best way to go, but its definitely the easiest...I already did it 3 times since the root came out XD
raynan said:
If you're not worried about your apps and data, you could always ODIN back to stock and start over. It may not be the best way to go, but its definitely the easiest...I already did it 3 times since the root came out XD
Click to expand...
Click to collapse
I read if you have the OTA version you can't ODIN back since the newer firmware is not out. I didn't get to the phone in time when it OTA'd. I will probably do that when the newer firmware is out. I am not anywhere close to a dev. So if I am way off base correct me its the only way I learn.
beeglej said:
I read if you have the OTA version you can't ODIN back since the newer firmware is not out. I didn't get to the phone in time when it OTA'd. I will probably do that when the newer firmware is out. I am not anywhere close to a dev. So if I am way off base correct me its the only way I learn.
Click to expand...
Click to collapse
Yes you can : http://forum.xda-developers.com/showthread.php?p=53454972
Swiping from dark side of Galaxy S5.
Hi Everyone:
I am attempting to root and install cm11 on my son's KFHD. I am a bit of a noob, but I have successfully rooted my nook color in the past and read MANY threads on how to root, but I'm kind of at a loss.
The problem is that I followed the thread on how to root and I had a bunch of trouble. I finally was able to get through the steps, but the command box closed before the KFHD rebooted successfully. In an attempt to "fix" it, I restored the device to factory settings. It seems to be working just fine with stock os, but there is a superuser app which has requested access to apps.
I downloaded an app from Mobile1 to check that there is root access and the app indicates that I do indeed have root access. Should I go ahead and try to install a rom?
I would like to root it because my son is using it for school and is having a hard time adjusting to the stock os. (Which I hate, too).
Thank you so much!!!!
-NDH
1. Super User is the app that lets apps have access to root. (easy way of understanding it)
2. You need to Install Twrp and 2nd bootlander before installing the rom.
go to this video and follow the directions carefully. http://www.youtube.com/watch?v=a1bLCuQN0-U
3.Go to this video to install cm 11 rom for 2012 version. http://www.youtube.com/watch?v=0ODVX_EYaVY
4. once intalled new rom go to settings-about tablet-cyanogenmod updates and then update to latest version. IMPORTANT
thank you
Thank you for the advice. I appreciate it.
I've run into a new problem today, however. The device powered itself off and won't reboot at all. (It had a full charge). So I am off to do some research on how to fix this problem. UGH.
-NDH
ndharvey said:
Thank you for the advice. I appreciate it.
I've run into a new problem today, however. The device powered itself off and won't reboot at all. (It had a full charge). So I am off to do some research on how to fix this problem. UGH.
-NDH
Click to expand...
Click to collapse
Did you flash anything before this happened?
nope
SafinWasi said:
Did you flash anything before this happened?
Click to expand...
Click to collapse
I didn't flash anything - just tried to root. After several hours of trying lots of fixes and googling like crazy, I was able to get the device to turn on. My WIN7 laptop was not recognizing the KFHD. I tried a different usb port on my laptop and it installed all of teh drivers and recognized the device.
I did go ahead and order a fastboot cable - and I'm glad I did. The day after I got the KFHD working again, it turned itself off again and would not reboot.
I spent several hours today trying to understand fastboot and how to use the cable and a few minutes ago, I was able to restore a system image and get it back to stock. I am waiting for it to charge up a bit and then I'll set it up again. I think it worked because there are no apps or anything installed as of now.
All I really want to do is have access to the Play Store and install an alternate launcher, so it looks and feels comfortable for my kid. He's had the kindle for almost a year, but doesn't feel very comfortable using it and its something he needs to use at school (where I can't help him). Once its charged up, I will re-root - following directions very closely!!!!!
Thanks for your help!
NDH
ndharvey said:
I didn't flash anything - just tried to root. After several hours of trying lots of fixes and googling like crazy, I was able to get the device to turn on. My WIN7 laptop was not recognizing the KFHD. I tried a different usb port on my laptop and it installed all of teh drivers and recognized the device.
I did go ahead and order a fastboot cable - and I'm glad I did. The day after I got the KFHD working again, it turned itself off again and would not reboot.
I spent several hours today trying to understand fastboot and how to use the cable and a few minutes ago, I was able to restore a system image and get it back to stock. I am waiting for it to charge up a bit and then I'll set it up again. I think it worked because there are no apps or anything installed as of now.
All I really want to do is have access to the Play Store and install an alternate launcher, so it looks and feels comfortable for my kid. He's had the kindle for almost a year, but doesn't feel very comfortable using it and its something he needs to use at school (where I can't help him). Once its charged up, I will re-root - following directions very closely!!!!!
Thanks for your help!
NDH
Click to expand...
Click to collapse
I would recommend you to install a custom ROM like CyanogenMod. Trust me,you'll love it. AOSP is much better than Amazon OS.
So, today I upgraded to 6.0 and had a hell of a time (took me 7 hours) and the problem was that when I installed su from twrp it'd soft brick my phone, anyway, that's not the problem, the problem is everything is saving to /storage/emulated and I can't access it without root. I noticed this when I was on OGInsta and I wanted to download a picture, it gave me an error code about how it couldn't find the directory, so I went to my file manager, everything was fine but I accidentally hit up instead of home and it brought me to an empty page. I started messing with the settings of my file manager assuming something went wrong with it, new version etc, and I found it had a root option. I clicked it and gave it root access and went back and I could see the files where I was previously. To make sure I tried to save something on kik, didn't work. I tried accessing my storage from the rar app and it wouldn't. I don't know what's going on or how it even got this way.
How did you install 6.0, what version of su did you install, and how did you fix the soft brick?
Sounds like you have very little idea what your doing and running a ton of random stuff. Probably best to do a system restore, take a step back learn what your doing and do it again properly... but if you can recount the steps you have done it may be fixable.
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat. I've never had so much trouble with something. And to answer your questions, I figured using nexus root toolkit would he fine, as it always has worked before but I couldn't get it to root my phone. It would soft Brick it for an unknown reason, I left it on for about an hour at one point to make sure it was bootlooping. So then I used adb, flashed boot.img and then recovery. Went into recover and flashed SU 2.52 beta. (this is also how I solved the soft Brick the nexus toolkit was giving me)
scryan said:
How did you install 6.0, what version of su did you install, and how did you fix the soft brick?
Sounds like you have very little idea what your doing and running a ton of random stuff. Probably best to do a system restore, take a step back learn what your doing and do it again properly... but if you can recount the steps you have done it may be fixable.
Click to expand...
Click to collapse
Also, to clearly, I have 2 storage paths. One is "sdcard/" and the other is "storage/emulated/0" I'm not sure if the "storage" folder is new in 6.0, I know 4.+ and 5.+ used "sdcard/". Too see "storage/emulated/0" I need to grant root access to the file manager. And any app the does not have root, cannot access that directory.
YoureVexing said:
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat. I've never had so much trouble with something. And to answer your questions, I figured using nexus root toolkit would he fine, as it always has worked before but I couldn't get it to root my phone. It would soft Brick it for an unknown reason, I left it on for about an hour at one point to make sure it was bootlooping. So then I used adb, flashed boot.img and then recovery. Went into recover and flashed SU 2.52 beta. (this is also how I solved the soft Brick the nexus toolkit was giving me)
Click to expand...
Click to collapse
you might have knowledge in making apps, but you are missing lots of knowledge when modding your phone. you are going to have to use an app like root explorer, and find where your storage was placed, then move it to the right location. or you can reflash the factory image. ive always just moved my storage back when its happened to me. anyways, flash the factory image the right way, not through a toolkit. then flash any custom kernel(if flashing marshmallow), and supersu.
YoureVexing said:
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat.
Click to expand...
Click to collapse
Why are comments like this always made by people who take 7 hours to flash a factory image, and make statements like
YoureVexing said:
So then I used adb, flashed boot.img and then recovery.
Click to expand...
Click to collapse
ADB cannot flash factory images.
I didn't need your resume... Just answers to the questions I asked....
Do as simms said and flash factory image with fastboot to fix whatever you did, then a kernel and the lastest supersu.
The emulated storage folder has been there at least since kit kat. My S4 and Moto X, neither of which saw LP both had it.
scryan said:
Why are comments like this always made by people who take 7 hours to flash a factory image, and make statements like
ADB cannot flash factory images.
I didn't need your resume... Just answers to the questions I asked....
Do as simms said and flash factory image with fastboot to fix whatever you did, then a kernel and the lastest supersu.
The emulated storage folder has been there at least since kit kat. My S4 and Moto X, neither of which saw LP both had it.
Click to expand...
Click to collapse
It took me 7 hours because I could figure out what was wrong with it and why twrp kept soft bricking my device. And I'm not worried about emulated. I know that has been there. I'm saying there is 2 folders, /sdcard and /storage. Every app is trying to use the path "/storage/emulated/0/*insert app folder here" and it cannot do that without root. I'm confused as too why all the apps are trying to do that for a default location instead of /sdcard. I've already tried to reflash everything. I even looked up like 5 tutorials to make sure I was doing it right and I was.
Can't really help you with your current situation (other than to advise you to flash a factory image and start over), but if it confirms your sanity the exact same thing happened to me using the rootkit to root my Nexus 6. I should've known better than to use rootkit, but I'm not really used to fastboot having been on Samsung devices and using Odin for everything. I corrected it by flashing a factory image, flashing the modified boot image, flashing TWRP, and then SuperSU. But the whole process was quite a fiasco from what I'm used to and for what I expected from a Nexus phone.
YoureVexing said:
It took me 7 hours because I could figure out what was wrong with it and why twrp kept soft bricking my device. And I'm not worried about emulated. I know that has been there. I'm saying there is 2 folders, /sdcard and /storage. Every app is trying to use the path "/storage/emulated/0/*insert app folder here" and it cannot do that without root. I'm confused as too why all the apps are trying to do that for a default location instead of /sdcard. I've already tried to reflash everything. I even looked up like 5 tutorials to make sure I was doing it right and I was.
Click to expand...
Click to collapse
/sdcard is a simlink, its the same folder.
internetpilot said:
Can't really help you with your current situation (other than to advise you to flash a factory image and start over), but if it confirms your sanity the exact same thing happened to me using the rootkit to root my Nexus 6. I should've known better than to use rootkit, but I'm not really used to fastboot having been on Samsung devices and using Odin for everything. I corrected it by flashing a factory image, flashing the modified boot image, flashing TWRP, and then SuperSU. But the whole process was quite a fiasco from what I'm used to and for what I expected from a Nexus phone.
Click to expand...
Click to collapse
The rootkit wasn't working for me, it's been a charm for my nexus 5 and from 4.+ and nexus 6 on 5.+, on 6.0 it wasn't working so I tried to flash it on fastboot and I still got the same thing. I'll try it once more I suppose, thank you.