So, I got this KF less than 24-hours ago and just gained root.
How I did this was not easy, painful, alarming and just plain scary, actually. But, I'm persistent and I have a 30-day return policy. :silly:
Anyway, I'm using Windows 7 X64-bit. I was kind of disappointed when I learned my Kindle Fire was a 2nd Generation (which I learned as I was following the 1st Generation root guide) because it had not been rooted yet and no guides were available.
At one point, I thought I had bricked it as the screen went black. I couldn't power down or anything and I ended up calling Amazon. They instructed me to hold the power button for 20 seconds until it shuts off, then plug in my power source and start it up. It fixed it and everything has been smooth since.
Ok, enough of that, here's how I gained root:
On the Device:
From the home screen, pull down the Notification bar and press "More..." on the top right corner of the settings bar.
Navigate to Device -> "Allow Installation of Applications" and set to "On".
Click Back then Security -> "Enable ADB" and set to "On"
Plug the Kindle Fire factory USB cord into the device and into the computer.
Hold down the power button and choose "Shut Down"
Push the power button again to Power on the device.
Now, assuming you have the android sdk in your system and drivers are all installed and adb recognizes the device
You can open a command prompt window from the folder where adb is located by holding SHIFT and right-click anywhere is the folder then choose "Open command window here". In the command prompt type:
Code:
adb devices
press enter and it should see your device.
If no devices are listed your drivers are not properly installed.
Once that was done, I proceeded...
The first thing I had tried was the Kinde Fire Utility
That was a complete waste of time and did nothing.
Then I tried another method that I had found on another forum HERE
At first, I kept getting errors:
Code:
[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied
So, I tried @sparkym3's method that same thread linked me to HERE.
That's when my device started flickering like crazy. I slowly navigated to the "Restore to Factory Defaults" in the Device option of the Settings menu. The device restored and everything looked fine until, out of nowhere, the screen flickered a bit, then went black. I could clearly see the device was on but, nothing was on the screen. When I pressed the power button it would blink green but, nothing would happen. So, I called Amazon's Kindle support line @ 1-866-216-1072 (I write that number because it is very difficult to find on their website).
They instructed me to hold the power button in for 20 seconds, they even counted with me, until the device shut off. Then, they had me plug the device into the wall using the plug (which did not come with the device, mind you) and power the device back on.
It worked and my device was fixed and then they told me to leave it alone and let it fully charge, which I did.
I decided i was just going to wait for someone else to root and not worry about it yet but, curiousity got the best of me and I decided once more to try the method listed HERE, which to my amazement, now worked. :victory:
The screen started to flicker a bit as I was going through the steps and I rebooted the device once more when all the steps were completed. I opened the superuser app and made sure it was updated. I downloaded and installed Titanium Backup from their website and allowed su permissions. The device is rooted and everything is working.
I hope this helps to those who wish to root their Kindle Fire (Non-HD) 2nd Generation.
**Also, as a note, my device is running the latest version 10.2.1.
And, I apologize for my poor spelling.
****
Once rooted, I installed "ES File Explorer" from their website and set the prefrences for root.
Then I followed THIS GUIDE and installed Google Play Store.
(2012-12-24) UPDATED ROOT FOR v10.2.4
I think there will be a lot more people in the 2nd Gen forum since the Cyber Monday sale. I figured I would save $70 and have a ghetto Nexus 7. Really wish I had done more research before I bought it because I had no idea there was even a 2nd generation Kindle let alone a locked bootloader.
I used the qemu method from the hd fire, worked like a charm, but only on 32bit windows. Now I have play store and so on but I am still thinking about returning it and going for the nexus 7.
Gesendet von meinem HTC Desire mit Tapatalk 2
davedophin said:
I used the qemu method from the hd fire, worked like a charm, but only on 32bit windows. Now I have play store and so on but I am still thinking about returning it and going for the nexus 7.
Gesendet von meinem HTC Desire mit Tapatalk 2
Click to expand...
Click to collapse
Rooting my kindle with the quemu method worked for me also, and i used Win8x64.
Only thing not working as expected is google calendar, it only uses the Amazon Version and this cannot sync multiple calendars like on my Galaxy R.
I bought one as well about a month ago, not knowing there was a "2nd gen" version. Boy was I shocked.. I returned it the next day. F'ing BS Amazon! You guys spend more money learning how to lock down these devices and stifeling development than it is worth.
akira02rex said:
I bought one as well about a month ago, not knowing there was a "2nd gen" version. Boy was I shocked.. I returned it the next day. F'ing BS Amazon! You guys spend more money learning how to lock down these devices and stifeling development than it is worth.
Click to expand...
Click to collapse
yeah **** them for selling a subsidized device and trying to get their money back...
stop whining if you are too lazy to inform youtself.
433Mhz said:
yeah **** them for selling a subsidized device and trying to get their money back...
stop whining if you are too lazy to inform youtself.
Click to expand...
Click to collapse
I'm sure Amazon is doing OK. Just returned mine. I'll pay the extra money for a nexus
I have just been bought one as a Christmas gift. I am more than happy with a £99 Kindle with 1gb ram and 1.2ghz dual core processor.
People are starting to root them, which opens them up slightly, which is a bonus. I've been burned with my Atrix, but I'm still happy with my £99 colour tablet.
I'm also quite confident that Amazon hasn't gone out of its way to lock the Fire down more than the Fire v1, so it should just be a matter of time before it's cracked wide open.
Sent using my Jelly fingers.
Well its been awhile since i have been here on the xda forums all they way since the touch pro 2 or tilt 2 whatever one came out last. Ordered my kindle fire 2 for whatever the discount price was last week and payed for overnight shipping got all excited the night before it shipped reading all the new roms i was gonna flash the next day and bam its the updated version so no go for roms but i did get rooted with the qemu method after a couple tries. biggest hurdle i has was when it says you may have to unplug your device and plug it in every time i had to do just that.
Once it's rooted, which play store apk are you using?
Google Play Store
obvious said:
Once it's rooted, which play store apk are you using?
Click to expand...
Click to collapse
I followed this method of installing Google Play store and it worked flawlessly. :highfive:
BookCase said:
I followed this method of installing Google Play store and it worked flawlessly. :highfive:
Click to expand...
Click to collapse
thats one i used and worked excellent and i also go go launcher ex working by reading through Here And got rid of the lock screen ads by following This So much better all around now!
Thanks I got my Kindle fire 2 rooted now (bought it on the last weekend cybermonday deal).
Am I right that atm there are no custom roms for the fire aviable? So the only option is to sit tight or take action and develope a methode myselfe?
HellSassa69 said:
Thanks I got my Kindle fire 2 rooted now (bought it on the last weekend cybermonday deal).
Am I right that atm there are no custom roms for the fire aviable? So the only option is to sit tight or take action and develope a methode myselfe?
Click to expand...
Click to collapse
That's correct.
Sent from my myTouch_4G_Slide using xda premium
Permissions problem - how did you fix it?
I am getting the permissions problem you had - driving me nuts! Any idea how to fix that?
BookCase said:
So, I got this KF less than 24-hours ago and just gained root.
How I did this was not easy, painful, alarming and just plain scary, actually. But, I'm persistent and I have a 30-day return policy. :silly:
Anyway, I'm using Windows 7 X64-bit. I was kind of disappointed when I learned my Kindle Fire was a 2nd Generation (which I learned as I was following the 1st Generation root guide) because it had not been rooted yet and no guides were available.
At one point, I thought I had bricked it as the screen went black. I couldn't power down or anything and I ended up calling Amazon. They instructed me to hold the power button for 20 seconds until it shuts off, then plug in my power source and start it up. It fixed it and everything has been smooth since.
Ok, enough of that, here's how I gained root:
On the Device:
From the home screen, pull down the Notification bar and press "More..." on the top right corner of the settings bar.
Navigate to Device -> "Allow Installation of Applications" and set to "On".
Click Back then Security -> "Enable ADB" and set to "On"
Plug the Kindle Fire factory USB cord into the device and into the computer.
Hold down the power button and choose "Shut Down"
Push the power button again to Power on the device.
Now, assuming you have the android sdk in your system and drivers are all installed and adb recognizes the device
You can open a command prompt window from the folder where adb is located by holding SHIFT and right-click anywhere is the folder then choose "Open command window here". In the command prompt type:
Code:
adb devices
press enter and it should see your device.
If no devices are listed your drivers are not properly installed.
Once that was done, I proceeded...
The first thing I had tried was the Kinde Fire Utility
That was a complete waste of time and did nothing.
Then I tried another method that I had found on another forum HERE
At first, I kept getting errors:
Code:
[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied
So, I tried @sparkym3's method that same thread linked me to HERE.
That's when my device started flickering like crazy. I slowly navigated to the "Restore to Factory Defaults" in the Device option of the Settings menu. The device restored and everything looked fine until, out of nowhere, the screen flickered a bit, then went black. I could clearly see the device was on but, nothing was on the screen. When I pressed the power button it would blink green but, nothing would happen. So, I called Amazon's Kindle support line @ 1-866-216-1072 (I write that number because it is very difficult to find on their website).
They instructed me to hold the power button in for 20 seconds, they even counted with me, until the device shut off. Then, they had me plug the device into the wall using the plug (which did not come with the device, mind you) and power the device back on.
It worked and my device was fixed and then they told me to leave it alone and let it fully charge, which I did.
I decided i was just going to wait for someone else to root and not worry about it yet but, curiousity got the best of me and I decided once more to try the method listed HERE, which to my amazement, now worked. :victory:
The screen started to flicker a bit as I was going through the steps and I rebooted the device once more when all the steps were completed. I opened the superuser app and made sure it was updated. I downloaded and installed Titanium Backup from their website and allowed su permissions. The device is rooted and everything is working.
I hope this helps to those who wish to root their Kindle Fire (Non-HD) 2nd Generation.
**Also, as a note, my device is running the latest version 10.2.1.
And, I apologize for my poor spelling.
****
Once rooted, I installed "ES File Explorer" from their website and set the prefrences for root.
Then I followed THIS GUIDE and installed Google Play Store.
Click to expand...
Click to collapse
johnnysnavely said:
I am getting the permissions problem you had - driving me nuts! Any idea how to fix that?
Click to expand...
Click to collapse
Try the Qemu method, or do what I did.
Sent from my myTouch_4G_Slide using xda premium
433Mhz said:
yeah **** them for selling a subsidized device and trying to get their money back...
stop whining if you are too lazy to inform youtself.
Click to expand...
Click to collapse
You still don't get it. Its not worth the time and money they put in to lock it down just as it is with every other phone or tablet put there. It ends up getting unlocked anyway - so what good did all of that do for them? NOTHING
Sent from my Galaxy Nexus using Tapatalk 2
akira02rex said:
You still don't get it. Its not worth the time and money they put in to lock it down just as it is with every other phone or tablet put there. It ends up getting unlocked anyway - so what good did all of that do for them? NOTHING
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It may be worth the time and money to Amazon because the longer it takes us to crack the bootloader the longer gen 2 owners will be getting all their apps and content from Amazon app store $$$$. They make it difficult buying them several extra months worth of elevated revenue. So far it seems to working as there are no custom roms and barely a solid root method Lucky for me I have the 1st gen rooted on custom rom sorry for the salt but I was thinking of getting a gen 2 so that's why I've been lurking over here.
Unsuccessful Root
I've got the Kindle Fire 7 HD, system version is 7.2.1_user_2040020.
I've tried the qemu root method which says it roots the device at step 5 but any app that tries to get root access like ES File Explorer is unable to do so.
I then tried this method:
----------------------------------------
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
adb reboot
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk
------------------------------------------
Every command takes and I don't get any permission denies but in the end no app is able to get root access.
Anybody have success rooting this device?
I also bought it with the Cyber Monday deal thinking I could flash it
When you guys say to do the qemu method you mean the one in this thread?
What drivers should I use? I have installed the drivers that come with KFU and I was able to flash my brother's KF1, I see that in that topic's attachments there is a zip of the KF HD drivers, are those the same drivers that I already have? If not, which one should I use?
Thanks
Related
I had an issue with my Desire Z where the screen got a bit of water in it (the rest of the phone seemed untouched). I tried the whole "drying it out with rice" trick, which didn't work at all, by the way In the end, I fitted a spare "top half" I had from a broken Desire Z. Everything works fine, except the touchscreen is reversed on the X axis. When I touch the left side of the screen, the right side gets activated, etc.
I tried using the original digitiser, but I've still got the same problem. Tried factory reset etc. Also I noticed I can't use the fre3vo to downgrade which I've done before on this very phone.
Any ideas?
Happened the same with mine under the rain. Waited a bit and come back to normality. It was very funny!
Anyways I'm sorry I can't help you!
virtualflyer said:
Happened the same with mine under the rain. Waited a bit and come back to normality. It was very funny!
Anyways I'm sorry I can't help you!
Click to expand...
Click to collapse
On the contrary, it's very helpful to know that others have had the same issue and it eventually came back. Thanks! How long did it take yours to return to normality?
It's possible the digitizer from the other phone is busted. I've bought a number of broken G2's from Ebay, and have a lot of spare parts. There's no guarantee that the digitizer will eventually work good. You might as well buy a new one. They're fairly cheap.
Gotta be careful with the fre3vo downgrade. Some guides work and some don't. I'll have to dig out which guide I use, but a common mistake people do is they copy the folder and not the file. If you accidentally copied the folder, you'll have to delete it. In adb shell, the command is "rm -R folder". Folder is the location of the files you accidentally copied. Give more details and I can probably help.
Dukenukemx said:
It's possible the digitizer from the other phone is busted. I've bought a number of broken G2's from Ebay, and have a lot of spare parts. There's no guarantee that the digitizer will eventually work good. You might as well buy a new one. They're fairly cheap.
Click to expand...
Click to collapse
I tried both digitisers - the other phone's digitiser was good before the ribbon cable went (I used it before it became a "spare"). Gotta be honest though, this feels more like a hardware/software problem than a digitiser problem though.
Dukenukemx said:
Gotta be careful with the fre3vo downgrade. Some guides work and some don't. I'll have to dig out which guide I use, but a common mistake people do is they copy the folder and not the file. If you accidentally copied the folder, you'll have to delete it. In adb shell, the command is "rm -R folder". Folder is the location of the files you accidentally copied. Give more details and I can probably help.
Click to expand...
Click to collapse
Cheers - I did the fre3vo downgrade fine on this phone before (and am a Linux Sysadmin for a day job so I'm comfortable with the procedure) but when I tried again, it just hung before it started scanning memory locations. Not sure what would cause that :S
That happened to me a while ago but it was because I flashed over another ROM without wiping first.
Sent from my Nexus 7 using xda premium
davetibbs said:
Cheers - I did the fre3vo downgrade fine on this phone before (and am a Linux Sysadmin for a day job so I'm comfortable with the procedure) but when I tried again, it just hung before it started scanning memory locations. Not sure what would cause that :S
Click to expand...
Click to collapse
Did you fallow this guide?
http://forum.xda-developers.com/showthread.php?t=1178912
When you get to the point when you do this.
adb push fre3vo /data/local/tmp
Make sure that fre3vo is a file and not a folder. Even if you do correct your mistake by copying the file and not the folder, you still have to delete the folder. Try using this command.
rm -R /data/local/tmp/fre3vo
Then copy the file. Otherwise my only other suggestion is to try this on another computer, or try updating your Android SDK.
Same thing happened to me; I just installed the HTC Calibrate. When I flashed another ROM onto my phone, the problem didn't return.
You could try HTC Calibrate if you're running a Sense ROM, but seeing how nivlac managed to fix his by flashing over, if you've got a non-Sense ROM, you could try that.
HTC Calibrate is available at the following thread: http://forum.xda-developers.com/showthread.php?t=1378142
Good luck!
davetibbs said:
On the contrary, it's very helpful to know that others have had the same issue and it eventually came back. Thanks! How long did it take yours to return to normality?
Click to expand...
Click to collapse
I think a quarter of hour... a bit less or a bit more...
Inviato dal mio HTC Vision con Tapatalk 2
Ok guys, i need the experts here. I just received a N7 tablet today off Woot.com for my wife for Christmas, so i unboxed it and turned it on.
Booted no problem and then i put on the charger. I turned it on because i wanted to install her games she plays on her phone so come
christmas day when she unwraps it the thing is ready to go. Well i left on charger and came back a few hours later and was prompted to install
OS update. I said to my self cool, no big deal. tapped it and it asked to update so i confirmed. The N7 shut down and loaded up with our favorite
little android with his chest cavity open for the world to see while he made himself better. But after some time he fell over and said ERROR!! i
said aw crap, and left it alone because i have seen this happen on my old HTC evo before and the phone recovered no problem. So i left it on
that screen and after a while the device did restart i thought ok good. But then it just got stuck on the Nexus loading screen, stayed on that for
about an hour before i started to get worried and looking online for help. Seems others have had this issue but i have not seen it on these
forums, although i did not look very hard either. So after reading and reading some more i went into bootloader and factory reset which did not
work. just stuck on nexus logo. i tried to install the update though the ADB sideload but always got an error saying invalid signature verification
failed. after reading some more found out the bootloader is locked and wont accept anything not signed. So i tried googles offical updates off
their site.Still got that error. Now i have looked into unlocking/rooting but you have to turn on USB debugging and also you seem to have to know
what version of android was on the device to start with which i never got a chance to look at. The website says it comes with 4.1 upgradable to
4.3. I have spend around 4-5 hours trying to get this working and i hope with the help of the people on here i can get it working so it can be a
great gift. If only i had gotten it from a store i could return it and have another one ready to go by the 25th but i know woot wont be fast to
exchange or asus if i have to go through them. Any and all help would be appreciated and thanks in advance for it. I am sorry i wrote so much.
N7 - android version----- unknown. possibly 4.1
Gen 1 or 2012 model
32 gig
wifi only
Try downloading Wug Fresh Toolkit. I used to use it all the time when I'd soft brick my Nexus 7 2012. It's a really simple tool to use and takes a lot of the guess work out of the equation. Should restore your device to stock, and it'll download whatever version of Android you specify for it.
If it works, I recommend going back and taking another crack at using ADB commands in the future, so you have a better understanding of the program under the hood. But for right now just get it up and running and ready for your lady to open on Christmas... Or at very least get it sent back in and get another.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.
well using that tool seemed to make the problem worse. Now the bootloader wont even load up. When tablet turns on it says boot failed in the top left hand corner and the google name is shown. in the top right corner it says start and i can use the volume keys to go up and down to select recovery mode, power off, start, and restart bootloader. but always come back to same screen with the google logo where it just says google in white. What else might i try?
Let me start this off by stating, I have found bootloader, but am unable to access it. Please keep reading because maybe you can. I'm running windows vista on a rather old laptop with just a gig of ram on a dual core, my computer is not fast enough to install the driver needed for fast boot (bootloader). I'm assuming you have basic knowledge of adb, if not please study up before you proceed
You will need to have
java, se developer toolkit, and SDK tools all installed. Look up tutorials on how to enable adb if your not sure what to do.
Sharps usb drivers
https://sh-dev.sharp.co.jp/android/modules/driver_eng/index.php?/sharp_adb_all/download
Steps
1ut phone into debugging mode and connect to PC
2: open your SDK directory and navigate into platform tools folder, once there hold shift + right click, click on "open command window here"
3.type "adb devices" should display bunch of numbers (your serial number) and say device next to it, this confirms adb is set up correctly
4. Disconnect phone and turn off
5. Open your device manager and make a mental not of where to sharp driver is
Next steps you have to be fast for, may take a few tries but your at no risk of hurting your phone so don't worry if you mess up a few times
6. While the device is powered off hold volume up + power, this will make the led at the bottom turn white for a brief period of time, there is sum confusion on if it turns blue or white due to me saying it was blue when I initially found this button sequence, it is white OK guys not blue, might have a blueish tint but the led is white in this mode mmkk.
7.plug in USB
8. The computer will prompt you to install a driver in a pop up window, it may work for you to just use this prompt but I had faster response just exiting out of this and double clicking the "unknown device" in device manager.
9. Click install driver
10. It will promt to identify what kind of device it is, click andriod.
11. It'll prompt to search for you or browse and find it yourself, click browse.
12. In the next window click "let me pick from a list of device drivers on my computer"
13. Click "have disk"
14.click browse and locate the folder with your sharp drivers, click "andriod_winusb" then OK, it should show 3 different drivers its going to install, one of which labeled bootloader, click ok it'll have a big pop up window just click yes on it.
The driver begins to install but the led turns off before it can and then disconnects. But now we know for sure where its at and a vaigue idea of how to get it, I know this isn't going along very fast guys and sorry I can't spend more time looking into it than I am right now. I believe Sharp didn't make the bootloader accesable through button sequences, we have to access it through the adb command "adb reboot bootloader" command after the drivers installed.
a big step
Amazing!!! Thank you for say about it!
Great
Seems like we are getting somewhere
keep this thread clutter free
We need a designated 306sh thread, all the 305 users flooded our original thread with unlocking and using in different regions, even though it clearly stated just 306sh users. So if you have a 305sh get off my thread, don't post here, Im serious I'll get mean, a lot of issues I had with adb were already being tested and the knowledge was posted. Just hard to obtain with all the 305 clutter. If your not testing and all your posting is a thank you, please just click like, though it is nice to read those lovely comments and thank yous but we need the thread clear for those willing to test their phones and post results. Don't post you agree, like the comment as I said if it doesn't directly pertain to testing there's no reason to post.
Canada Unlock
Hey guys, I just bought this phone (306SH) and I am from Canada.
I really fkn love this phone, it appears to be better then my Samsung Galaxy Note 3 with it's style, speakers and even the screen is solid. Do you guys think there is any hope for a unlock in the near future? I bought the phone because it was dirt cheap and I was hoping in the near future I could switch when the time was right. Let me know your thoughts and where we're at right now with unlocking it.
Thanks
No. Clicking "Let me pick from a list..." then "Have disk" and selecting a driver location just shows all the available drivers in that location. It doesn't verify against the hardware ID (USB\VID_XXXX&PID_XXXX&REV_XXXX).
If you click "Have disk" and open iPod drivers, it'll show iPod drivers. Did your phone magically turn into an iPod? Probably not.
i use adb for 306sh for a long time -_-, and how to unlock boot, i tried adb reboot bootloader and reboot recovery, it just turn on again -_-
GUYS!!!!!!
Guys i contacted kingoroot and they said they are working on supporting the 306sh, cant wait!!!!!!!!!!!!!!
Yaaaaaaaaaaaasssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
-------------------------------------------------------------------------------------------------------------------------------------
Jared's360SH said:
Guys i contacted kingoroot and they said they are working on supporting the 306sh, cant wait!!!!!!!!!!!!!!
Yaaaaaaaaaaaasssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
-------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
wao, you are amazing
I've contacted them months ago and they said the same thing, so don't get your hopes up too high.
jamer123 said:
I've contacted them months ago and they said the same thing, so don't get your hopes up too high.
Click to expand...
Click to collapse
Ya I've tried kingo as well, right now just an empty promise.
edit
Edit: PLEASE fact check ANY website that claims to have any sort of "solution" to anything found here.
Yea hopefully XDA can get it shut down before someone tries it.
sounds great
i cant wait for this to work i want root so bad so i can mess with my pjone and make it be the way i want!
etirkca said:
No. Clicking "Let me pick from a list..." then "Have disk" and selecting a driver location just shows all the available drivers in that location. It doesn't verify against the hardware ID (USB\VID_XXXX&PID_XXXX&REV_XXXX).
If you click "Have disk" and open iPod drivers, it'll show iPod drivers. Did your phone magically turn into an iPod? Probably not.
Click to expand...
Click to collapse
yes you are right ..
but i still think with " hold volume up + power" is enter in bootloader.. but we don't have right drivers..
loonbg said:
yes you are right ..
but i still think with " hold volume up + power" is enter in bootloader.. but we don't have right drivers..
Click to expand...
Click to collapse
hold volume up + power just enter recovery with no connect adb to device
irishobo said:
Yea hopefully XDA can get it shut down before someone tries it.
Click to expand...
Click to collapse
Yo! Long time man! You have this phone now?
Modding.MyMind said:
Yo! Long time man! You have this phone now?
Click to expand...
Click to collapse
Yes sir! How is the new kid?
Hi,
I am starting this thread hoping to find a solution to backup the working tablets so we will be able to revive them despite the kill switch being triggered.
The only solution so far seams to be by using nvflash in apx mode.
So far I have managed to boot my tablet in APX mode, but I have not done any other testing.
The tablet (still not killed one) is recognized by computer as being in APX mode.
Requirements:
1. Rooted tablet
2. Terminal app from Google play
Commands issued for APX mode:
1. Open terminal app and write "su" followed by enter to get root
2. Write "reboot" and press enter while keeping the volume up key pressed
Let's continue!
OP's 2nd post deleted - no need for it. Just edit Post #1
LenAsh said:
OP's 2nd post deleted - no need for it. Just edit Post #1
Click to expand...
Click to collapse
where are or name from other post, this thread is very important for us research and i think could useful.
thanks for advance.
I just received my replacement tablet a few days ago. My device has never been rooted or anything prior. I turned on the new device and started using it. I went back to my old device (connected to wifi and everything) and it still boot and i was able to use it all night. 2 days later I tried to use it and it powered on and everything was fine. I just rooted the mofo and installed a custom rom. I never seemed to have received the "kill switch"
The note in my package said to dispose of the device. So... I guess I now have 2 shields. My battery has never gotten warm, I dont use it very often though.
JuStAdsor said:
Hi,
I am starting this thread hoping to find a solution to backup the working tablets so we will be able to revive them despite the kill switch being triggered.
The only solution so far seams to be by using nvflash in apx mode.
So far I have managed to boot my tablet in APX mode, but I have not done any other testing.
The tablet (still not killed one) is recognized by computer as being in APX mode.
Requirements:
1. Rooted tablet
2. Terminal app from Google play
Commands issued for APX mode:
1. Open terminal app and write "su" followed by enter to get root
2. Write "reboot" and press enter while keeping the volume up key pressed
Let's continue!
Click to expand...
Click to collapse
I don't really understand the issue here, can you confirm that the tablet is still active cf. not hit by the killswitch? Why would you get an apx connected message? On a working tablet you would be directly send to an adb/fastboot interface? Usually only the killed tablets would be recognized as apx when you then connect it to a pc.. People are looking for a solution on how to nvflash via apx mode, which is an nvidia proprietary protocol and probably won't be pushed any time soon, if ever.. Possible solutions are moving to linux at the moment, where people try to connect their bricked tablets in apx mode hoping that linux would recognize the drivers, eventually, and maybe use open source universal flashing tools to recover their bricked devices..
doomedromance said:
I just received my replacement tablet a few days ago. My device has never been rooted or anything prior. I turned on the new device and started using it. I went back to my old device (connected to wifi and everything) and it still boot and i was able to use it all night. 2 days later I tried to use it and it powered on and everything was fine. I just rooted the mofo and installed a custom rom. I never seemed to have received the "kill switch"
The note in my package said to dispose of the device. So... I guess I now have 2 shields. My battery has never gotten warm, I dont use it very often though.
Click to expand...
Click to collapse
Yes, your tablet is still alive because you flashed another rom (and that's exactly what you should do to be sure to never get hit by the kill switch) - it is very likely that the kill switch isn't triggered immediately, and than the silent update might not hit immediately neither, you're very lucky, most of the people were hit in very few hours, they couldn't even get their research done before the trigger - that said: the best way is to root the old tablet before setting up the new one, and deleting tegraota.apk and its parent directory - as explained in bogdacutu's thread in this very forum, and/or flashing a new rom to not have any nvidia apps anymore.. You can do both if you even use multirom port for nvidia shield tablet.. I can manifest that all this is working since i did it - i tryed it all and do have 2x tablets now like many others too
This isn't cool man, why steal from Nvidia? Or from anyone. Stealing is not OK.
Sent from my SM-N910T
not stealing XBlack, my tablet was getting hot before recall...I did researched and spent time and efforts to fix the issue which i did. Nvidia sends new tablets to cover their ass for potential law suites in case of a situation happening again. Specifically states to dispose or return and why return if they will dispose for you? Why dispose of a tablet when the user fixed it by the user community. Is it taking advantage YES, we are smart people, we fix it. It was their choice to send new tablets without having to receive old ones prior. In no way is it stealing, tucking it in my pants and walking out of a Best Buy or FRYs without paying for it is stealing. We as a community with fixed tablets can be looked at as beta testers who get to keep their prototype and are given a NEW updated consultation model. Pretty much sums it up you can look at it in any way you like but we as a smart community in no way are criminals that steal from NVIDIA. Thanks NVIDIA i will forever be a loyal customer who buys your products since i think they are great. thank you for my new updated tablet.6
The problem is if you "fix" the tablet and then give it to else, and it catches fire, will nvidia be liable? They want the defective devices off the street, not disassembled and reassembled with non spec parts by potentially incompetent consumers.
Sent from my HTC M9 using Tapatalk
I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.
chrisrf said:
I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.
Click to expand...
Click to collapse
Did you convert your tmobile to international ? I guess you did. So either root it and install magisk or livr without Google pay.
Sent from my [device_name] using XDA-Developers Legacy app
chrisrf said:
I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.
Click to expand...
Click to collapse
When you go to About phone the build number will tell you if it is T-Mobile converted phone. If the build number starts with ONEPLUS A6013_34_ then it is converted, if it starts with ONEPLUS A6013_41_ or ONEPLUS A6010_41_ then it is a global version.
Krzysiek_CK said:
When you go to About phone the build number will tell you if it is T-Mobile converted phone. If the build number starts with ONEPLUS A6013_34_ then it is converted, if it starts with ONEPLUS A6013_41_ or ONEPLUS A6010_41_ then it is a global version.
Click to expand...
Click to collapse
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?
chrisrf said:
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?
Click to expand...
Click to collapse
Well you can't do really anything but if you have not had it too long you could return it.
chrisrf said:
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?
Click to expand...
Click to collapse
You have 3 options:
1. DO nothing and hope OnePlus will fix it down the road. I actually lost hope with this one.
2. Load T-Mobile version, and loose dual sim capability. Google Play will pass certification and Google Pay will work.
3. Use Magisk, at your own risk, to trick SafetyNet check.
I have one of those scammy "no warranty" T-mo -> Intl. OnePlus 6T and, with enough work, it is possible to convert to the most recent Intl. android 10, and get root and Google pay working. I don't think at this time it's possible to watch Netflix in HD while having your cake and eating it too, sadly. The A/B situation on this phone is painfully confusing and leads to brick after brick as you learn the ropes of this phone. Not sure that's TMo's fault. Thankfully the bricks are fixable. You need the modded flasher for 9.0.11. From usb serial mode, the flasher gives some gibberish "Sahara" error. There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..." -- What worked for me was holding down all the physical buttons, vol+, vol- and power, with the red "Saharah, please fix..." (something like that) red error message blinking away at me on the computer screen, and the phone plugged in to computer USB, the whole time. Only when its air composition sampling system detects your fingers bleeding profusely, will it kick in and fix your bricked device
So that gets you to an equivalent to a locked Global 9.0.11 rom with no OTA updates. From there you can do developer mode -> unlock bootloader instantly from fastboot -> (loose all your data) -> TWRP; now the a/b stuff gets really confusing AF but if you do TWRP from fastboot->flash 10.3.2 -> TWRP from fastboot again (it's like ms windows!) -> flash TWRP .zip installer -> TWRP from fastboot yet again -> Magisk, you can finally boot system.
To pass CTS profile you'll need to use the command-line signature changer Magisk module and Magisk Hide. Once the play store says it's "Certified" (certifiable more like...) and Magisk is giving you two green checkboxes, you are ready for more suffering. Now you need to freeze the Google Pay/Play apps and Google Play services and blow away all their data. At least that's what I did. Then make sure Magisk hide has all the Google play/GMS/AR/pay stuff hidden in Magisk, one more reboot for good measure, and you're off to the races. This gets Google Pay working and even lets you watch DRM at Widevine L3 level... it's still not all your cake and all your eating I suppose... hopefully you're not a big Netflix guy. Otherwise you kinda bought the wrong phone.
GL! Oh btw I have not found any way to restore an encrypted TWRP backup on this device. Starting to suspect it's literally impossible at this time -- but, if I'm honest, probably I just haven't gone through enough suffering, yet, to figure it out.
anonywimp said:
There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..." -- What worked for me was holding down all the physical buttons, vol+, vol- and power, with the red "Saharah, please fix..." (something like that) red error message blinking away at me on the computer screen, and the phone plugged in to computer USB, the whole time. Only when its air composition sampling system detects your fingers bleeding profusely, will it kick in and fix your bricked device
Click to expand...
Click to collapse
Nope. Just completely dis-confirmed the above recipe. I am clearly still well in the cargo-cult phase of my OP qdl client tools education
All I can say for sure is randomly frobbing with the buttons and the phone-side usb-c cable for long periods of time will usually eventually start the process. And one sure-that-I'm-not-sure---but-still-fairly-confident correction: It probably helps to /un-/plug the phone from the PC, once it starts giving the meaningless red "Sahara quintessence frobnitz poop" error message (or whatever equally meaningful thing it actually says). If you find yourself in TWRP, you can use the "Reboot edl" button. Likewise, I believe the stock recovery has an interface to jump to qdl mode... could be making that up though Anyhow I think from there you want to turn the phone entirely off, which I believe can only at this point be achieved through continuous, uninterrupted mashing of the power button. So just after your get the error and disconnect, is your opportunity to impress the phone by bleeding all over it.
anonywimp said:
You need the modded flasher for 9.0.11. From usb serial mode, the flasher gives some gibberish "Sahara" error. There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..."
Click to expand...
Click to collapse
OK, I think I figured out an actual recipe now, or the beginnings of one. It is still a bit fuzzy in places. It goes like this:
If you're not in qdl mode, or you are there but it won't talk to the proprietary flasher software, get the phone completely turned off. Often this is the hardest part. I have sometimes managed to brick my phone where it will Boot and insta-freeze at the infuriating-yellow-triangle screen¹. Then it will just sit there, indefinitely, and never bring up any sort of USB or wifi connectivity (nor does it show any sign of boot-looping, judging by dmesg output on my computer. It's just cold, and dead. Probably a bootloader bug/secure boot fail). In every semi-brick-like circumstance like this, I've found the following enables me to get the phone to turn itself off reasonably quickly, in fact, in just a couple of seconds, usually: unplug any USB-C cable (so I'm running on batteries), hold down all the buttons* until fingers bleeding or something happens -- if nothing happens, release all the buttons briefly and try again; once off, release all the buttons immediately.
Now get the phone back on, and in qdl mode. Somehow. Usually, if the phone is unplugged and off, I can get it there by holding all the buttons and plugging it into usb. If I'm soft-bricked, I'm already there, so nothing to do. From TWRP I can easily "reboot edl" to get there. Maybe there's ways to do it from fastboot, stock recovery, and system as well, via adb/fastboot commands.... My preferred way is holding "all the buttons" for about 1 second, and plugging in the usb cable, which will cause it to enter qdl mode "just one time" without actually bricking anything.
Now, finally, we run the proprietary flasher tool. Press start and it will go until it gets to the "sahara bingo yip-a-dee-ha" error (or whatever it really says... definitely not exactly what I wrote ).
Now turn the phone off again. Same recipe, but this time it seems to almost-always suffice to keep the phone connected to USB, while holding all-the-buttons. If that isn't working, then I go ahead and unplug, power cycle, and get into qdl mode like above. During this, the computer software is maybe completely disconnected from your phone, *****ing and moaning the whole time about Sahara or whatever. Ignore that, it's fine.
If the phone was fully powered off (rather than power-cycled in place), be sure to next release all the buttons, so that the phone has no usb or button-press input of any kind for at least a fraction of a second. Then press "all the buttons" again (nb: I suspect just vol+ and vol- suffice here, and the power button is superfluous? Maybe even detrimental depending on ordering? If I screw this up (sometimes it winds up booting into recovery or bootloader), then I find a way to ask it to reboot from there into qdl mode, if I can, or else power off from there and try again to use the three buttons.
pro tip said:
It is possible to hold all the buttons for too long. In which case, you may find yourself booting system. From there you may need to start this guide over from the beginning, sorry. The correct period of time to hold all the buttons down is about a second. Two seconds is probably too long.
Click to expand...
Click to collapse
Using your fourth hand, Plug in a USB-C cable, what leads from your computer, to the phone, while continuing to hold down all the buttons with your other three hands (or, if you entered qdl via software, just plug it in, now).
That's it, done. Kick back and enjoy as the tool's progress bars go wild and unbrick your phone tut suite. The qdl process should be able to go all the way to the end where it says "100%" (although when you close the program it will still treat this like you are interrupting it in the middle; I think that's because it does multiple phones at once, and you only ever fed it the one phone, so it is alerting you that, hey, phone #2 never got processed).
I am doing the above in a non-FOSS emulator under desktop linux, using the patched client referenced from xda threads.
I imagine qemu would work, as well. Obviously native Windows is going to be your best bet. I def. wouldn't trust Oracle (VirtualBox) USB emulation with my qdl flashing needs, if I were me -- which I am. Phones tend to look like huge USB hubs, full of an ever-changing kaleidoscope of peripherals. Which I don't think the VirtualBox USB stack is really ready to cope with right now. (Not even with the proprietary USB add-on pack or whatever that is -- I simply don't trust Oracle not to hard-brick my phone; VirtualBox has seemingly perma-bricked one device for me, already. That was some time ago but I'm not going to feed it any more devices and I doubt the USB was fixed in vbox. It think it's paravirtualized, or something, so as to be super-fast, but unreliable when the bus topology changes in meatspace.
-- rants / footnotes ---
¹ You know, that warning screen for "security." Which, currently, happens to be punishing me for trying to put the newest stock security updates onto my phone that I just purchased a month ago¹*².
* Not an "All the things" meme -- by "all the buttons" I literally mean all the hardware buttons: [vol+], [vol-], and [power].
¹*² I imagine the person who made the decision to require this in Android would explain it something like this:
straw man said:
(California accent) "Um, like, why? Are you a criminal or something? You know, you could just buy a new phone for like $899 US. Oh, you're, like, poor, or something? Well, OK, I guess there's no way for us to stop you from doing that. But we, like, won't be able to support you in any way. Also, sorry, but we're just going to need to put a brief warning screen on your phone, as a safety measure? No, it's not really a warning for you. More, like, in case other people might be around you for some reason? It just says, 'Hey, no judgement, but it seems like maybe a poor person owns this phone? And they're definitely doing some really weird stuff with it. So just be careful. Like maybe tell a friend where you're going, if you're going to spend time with them.' What? No, I'm sorry, there's no way to remove it. We paid millions to have it fused into the microchips or something? If you could just remove the warning, that would defeat the purpose. So, I'm sure you'd want the people around you to be safe, right? And, like, so do we! So we, like, locked that down pretty tight, yehh-...!'
Click to expand...
Click to collapse