Database Users

[Q] Nexus 7 reboots to former state constantly

Hi My 2012 nexus 7 16gb wifi updated to 4.3 and since September 11th it will not factory reset, remote reset, sideload updates or unlock bootloader.
Every boot the same app update, even if I updated them all in previous boot minutes earlier, the nexus randomly reboots It's self too.
If I delete the data it returns on reboot, nothing I can do gets a different outcome, I'm not keen on returning it as is as all my data and accounts can be accessed in current state, even credit card through google play!
I waited for 4.4 to be released in the hope the update might cure this, but I cannot update it, please advise on how I might fix this or completely wipe my nexus?
Thanks

Use wugfresh's toolkit to redo your install. It will restore it to a factory state. The only problem people seem to have is getting the drivers installed properly, so it may take you a little while. Just be patient and follow the instructions and/or go to the thread for help.
http://forum.xda-developers.com/showthread.php?p=28616745
Sent from my Nexus 7

mssam said:
Use wugfresh's toolkit to redo your install. It will restore it to a factory state. The only problem people seem to have is getting the drivers installed properly, so it may take you a little while. Just be patient and follow the instructions and/or go to the thread for help.
http://forum.xda-developers.com/showthread.php?p=28616745
Sent from my Nexus 7
Click to expand...
Click to collapse
Hi have tried every option on the toolkit, adb and fastboot drivers are working ok, but it reboots as part of the install and goes back to previous state!
also tried http://blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
and got this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What options did you select? Did you try Flash Stock +Unroot >Current: Soft-Bricked/Bootloop? I actuary have a n7 2012 that I need to redo to factory state, so I'm going to do that with wugfresh's toolkit and see where we differ...
Sent from my Nexus 7

mssam said:
What options did you select? Did you try Flash Stock +Unroot >Current: Soft-Bricked/Bootloop? I actuary have a n7 2012 that I need to redo to factory state, so I'm going to do that with wugfresh's toolkit and see where we differ...
Sent from my Nexus 7
Click to expand...
Click to collapse
Hi, I have tried every option, even the advanced options, part of the process is booting and as soon as the nexus reboots its back to original state, same with factory reset :crying:

That is strange. If you did fastboot erase user data and that didn't wipe everything idk. What about mskip's toolkit? I remember a while back wugs kit didn't work for me, but mskips did. Did you try his toolkit?
Sent from my Nexus 7

mssam said:
That is strange. If you did fastboot erase user data and that didn't wipe everything idk. What about mskip's toolkit? I remember a while back wugs kit didn't work for me, but mskips did. Did you try his toolkit?
Sent from my Nexus 7
Click to expand...
Click to collapse
Hi, yes I tried version 5.0 with no joy!

This is what happens when I try to adb sideload image-nakasi-krt16o.zip
Signature verification failure
So when I'm there I do a factory wipe, all successful till I reboot and everything is as it was previously!

scumgrinder said:
This is what happens when I try to adb sideload image-nakasi-krt16o.zip
Signature verification failure
So when I'm there I do a factory wipe, all successful till I reboot and everything is as it was previously!
Click to expand...
Click to collapse
I just flashed the 4.4 update on the nexus 7 2012 using wugstoolkit. At first when I downloaded the factory image and tried to flash it, it wouldn't wipe the tablet like you said and flash the update. Then I started playing with the locks. I think I chose to relock it, unlock, then flash stock + unroot and it worked. If you haven't figured it out, that's what it seemed to take for it to work for me...

mssam said:
I just flashed the 4.4 update on the nexus 7 2012 using wugstoolkit. At first when I downloaded the factory image and tried to flash it, it wouldn't wipe the tablet like you said and flash the update. Then I started playing with the locks. I think I chose to relock it, unlock, then flash stock + unroot and it worked. If you haven't figured it out, that's what it seemed to take for it to work for me...
Click to expand...
Click to collapse
It won't unlock! The 4.4 ota update downloaded, but it to led to 'no command' then reset to original state as always.

scumgrinder said:
It won't unlock! The 4.4 ota update downloaded, but it to led to 'no command' then reset to original state as always.
Click to expand...
Click to collapse
I followed those instructions from laptopmag and the worked to the tee. You shouldn't have needed to sideload anything. You had it unlocked at first, so what do you mean "it won't unlock?" You can see it in your screenie below, and I can also see that the fastboot commands were working so there wasn't a driver problem. What did you do after you did the fastboot oem unlock command in the screenie below? Did you fastboot the bootloader, then the factory image.zip? It looks like everything was working for you as it should, so what happen? I've done the laptopmag instructions two times and every thing is working fine for me; the tablet was erased both times as well. I'm curious at what point in the laptopmag instructions are you experiencing the problem?
scumgrinder said:
Hi have tried every option on the toolkit, adb and fastboot drivers are working ok, but it reboots as part of the install and goes back to previous state!
also tried http://blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
and got this
Click to expand...
Click to collapse

mssam said:
I followed those instructions from laptopmag and the worked to the tee. You shouldn't have needed to sideload anything. You had it unlocked at first, so what do you mean "it won't unlock?" You can see it in your screenie below, and I can also see that the fastboot commands were working so there wasn't a driver problem. What did you do after you did the fastboot oem unlock command in the screenie below? Did you fastboot the bootloader, then the factory image.zip? It looks like everything was working for you as it should, so what happen? I've done the laptopmag instructions two times and every thing is working fine for me; the tablet was erased both times as well. I'm curious at what point in the laptopmag instructions are you experiencing the problem?
Click to expand...
Click to collapse
It all appears to unlock, but lock state staus is always Locked
same as factory reset works fine, till it reboots to its default state!
I'm convinced its a hardware issue

I have EXACTLY the SAME problem
It really is an impossible problem. NOTHING will fix it!
I too am convinced it is a hardware problem.
I have given up & bought a 2013 version.
Let us know if you succeed....
scumgrinder said:
It all appears to unlock, but lock state staus is always Locked
same as factory reset works fine, till it reboots to its default state!
I'm convinced its a hardware issue
Click to expand...
Click to collapse

Never got this fixed, still in a drawer, anyone got any ideas?

The same thing happened to my 2012 as well.

[Q] No matter what I can not get into recovery

Hello,
I have a co-workers Sprint LG G2 (lg ls 980)phone and I thought this would be a simple process to root. I mess with Samsung's and HTC all the time.
I have it rooted and super user is fine. I wanted to put on TWRP so he can flash different roms and themes.
The phone works great I just cant get into recovery. I tried an app called flashify and quick boot and nothing works.
So I went the old school way, probably should have done it that way from the start and pushed with adb. It shows its fine like always.
I tried that quick boot again and all I get is this message.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas would be great. I have also downloaded
Sprint LG G2 Back To Stock.zip
I was hoping there was an easier fix than doing this.
Thanks in advance.

If you can boot into system and have working adb just plug in and type
adb reboot recovery
Sent from my LG-G2 using XDA Premium 4 mobile app

riggsandroid said:
If you can boot into system and have working adb just plug in and type
adb reboot recovery
Sent from my LG-G2 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have done that and it still brings me to the same screen.

Sample usage
=============
First, a developer must pull the aboot image from a target device:
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)
if you pull the aboot I could try patching twrp for the phone

It's up and running.. I had to use LG reset tool
Sent from my HTC One using Tapatalk

budeone said:
It's up and running.. I had to use LG reset tool
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I probably tried that but link for the LG Reset tool. Glad you got you brought it back to life. hehe

budeone said:
It's up and running.. I had to use LG reset tool
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I do not have any issue but can you tell us what is LG reset tool? May be it will come handy for others. thanks.

dps33 said:
I do not have any issue but can you tell us what is LG reset tool? May be it will come handy for others. thanks.
Click to expand...
Click to collapse
I started here and after I read and followed the directions it was pretty easy.
http://forum.xda-developers.com/showthread.php?t=2432476
His phone went back perfect.. I rerooted and he has a custom rom.

Ok I'm trying to use the same method of resetting and I'm getting the error "Download FAILED!" in red and " "Device model is different!" & "Check phone or dll." However I'm 100% sure I got the right firmware and dll and device model is correct. I've done that exact guide over and over for the past 11 hours and some other ones too. My brain is hurting, I can't boot into recovery for some reason and I'm stuck in a boot loop.

You have to be in download mode. Make sure com port is set right
Sent from my HTCONE using Tapatalk

budeone said:
I started here and after I read and followed the directions it was pretty easy.
http://forum.xda-developers.com/showthread.php?t=2432476
His phone went back perfect.. I rerooted and he has a custom rom.
Click to expand...
Click to collapse
Does this method remove the root? I'm just wondering as I've read a few posts about people having issues with OTA updates with rooted phones. My phone is rooted and I'm trying to figure out the best/safest route to follow once KitKat if officially released.

RPAusCan said:
Does this method remove the root? I'm just wondering as I've read a few posts about people having issues with OTA updates with rooted phones. My phone is rooted and I'm trying to figure out the best/safest route to follow once KitKat if officially released.
Click to expand...
Click to collapse
yes, I was unrooted like out of the package.

[Q] Stuck on stock recovery

Good morning again.
After my recent post about my cellphone as half-dead, I'm looking for rescue the information on the Internal Storage (We are talking of almost 3.5 GB of personal information). I know what ANY custom recovery can help me with this mission...
But after almost 4 hours trying with no success, I don't know what to do. :crying:
Step 1: Plug USB cable
Step 2: Vol+ Vol- and Power Button
Step 3: Select AP Fastboot
Step 4: On cmd write fastboot flash recovery "name of recovery here with .img"
On this step, I ALWAYS got this:
(bootloader) Variable not supported!
target max-download-size: 30MB​Step 5: On cmd write fastboot reboot
Step 6: As fast as you can, press Vol+ for enter to the recovery
Alright. That's the process what everyone's using, right? Well, it isn't working for me, as I got always to the same recovery :s
Android system recovery <3e>
KDA20.62-10.1​
What can I do? I used even the guide of ATTACK [GUIDE][FAQ][KK] How to Root, Boot Unlock & More
With no success...
I have Stock KK 4.4.2 what ends in .15 and Unlocked Fastboot

What recovery file are you trying to flash? Also, are you using the Moto fastboot? I believe this issue happens if you are using normal fastboot. Mfastboot is downloadable from that thread you linked
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk

xKroniK13x said:
What recovery file are you trying to flash? Also, are you using the Moto fastboot? I believe this issue happens if you are using normal fastboot. Mfastboot is downloadable from that thread you linked
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
Click to expand...
Click to collapse
Uhm... I downloaded the mfastboot file what the guide had...
Download Mfastboot [MIRROR] - Refer to Mfastboot setup
Click to expand...
Click to collapse
I just unzip it on a empty folder (C:\Motorola RAZR M XT907\MFastboot in this case) and used mfastboot what he says on the guide.
I'm trying to flash any of these 3 recoveries:
TWRP-2.8.2.0-RAZR_M_KKBL.img
TWRP2710-RAZR_M-KITKAT.img
CWM6049-RAZR-HD_M-KITKAT.img

xKroniK13x said:
What recovery file are you trying to flash? Also, are you using the Moto fastboot? I believe this issue happens if you are using normal fastboot. Mfastboot is downloadable from that thread you linked
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try putting it somewhere with no spaces in the path, like C:\xt907
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk

xKroniK13x said:
Try putting it somewhere with no spaces in the path, like C:\xt907
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
Click to expand...
Click to collapse
Still same problem (6 failed attempts with every recovery)... I think I'm going to need learn how to use HouseOfMoto (I don't have ANY idea how to use it).

Use Flashify.
Sent from my Moto G™

ATTACK said:
Use Flashify.
Sent from my Moto G™
Click to expand...
Click to collapse
Uhm sorry... But how I'm going to use flashify if I'm trying to recover the information from a damaged Android?

Pedreo1997 said:
Uhm sorry... But how I'm going to use flashify if I'm trying to recover the information from a damaged Android?
Click to expand...
Click to collapse
You never stated that you couldn't boot to the OS in the OP.
After reading your other post, I believe you have a bad eMMC(?) and your device may be stuck in R/O. If that is the case your phone is non-recoverable. Your only option is to 'try' and restore via RSD or similar - but its unlikely to fix the issue.
Sent from my Moto G™

ATTACK said:
You never stated that you couldn't boot to the OS in the OP.
After reading your other post, I believe you have a bad eMMC(?) and your device may be stuck in R/O. If that is the case your phone is non-recoverable. Your only option is to 'try' and restore via RSD or similar - but its unlikely to fix the issue.
Sent from my Moto G™
Click to expand...
Click to collapse
Well sorry...
I don't know how I got the cellphone to work... and then I made a mistake and well :/
After use HouseOfMoto, my cellphone finally got out of the bootanimation, but constantly ending com.android.phone
I got the idea of put the cellphone on Airplane mode. The cellphone is again on the same problem :crying:
Do you know how it worked the first time? And if that is a sign of life?

Pedreo1997 said:
Well sorry...
I don't know how I got the cellphone to work... and then I made a mistake and well :/
After use HouseOfMoto, my cellphone finally got out of the bootanimation, but constantly ending com.android.phone
I got the idea of put the cellphone on Airplane mode. The cellphone is again on the same problem :crying:
Do you know how it worked the first time? And if that is a sign of life?
Click to expand...
Click to collapse
Did you perform a FULL install on House of Moto? What FXZ did you use? Maybe try redownloading or confirm hashes to make sure there just wasn't an issue with the FXZ.
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk

xKroniK13x said:
Did you perform a FULL install on House of Moto? What FXZ did you use? Maybe try redownloading or confirm hashes to make sure there just wasn't an issue with the FXZ.
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
Click to expand...
Click to collapse
Uhm... What do you mean with FULL install? Remember what I'm trying to recover some folders if it's possible. Stock recovery, and I'm using VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml.zip and believe me: The only available download site lasts downloading 6 hours. It's A LOT of time.

Pedreo1997 said:
Uhm... What do you mean with FULL install? Remember what I'm trying to recover some folders if it's possible. Stock recovery, and I'm using VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml.zip and believe me: The only available download site lasts downloading 6 hours. It's A LOT of time.
Click to expand...
Click to collapse
You never noted that you wanted to recover things. I'd deal with the phone app force quitting and copy things to your computer via the USB. After you get everything you need, try a full wipe. If you don't want to do a re-download of the firmware, at least verify the hashes. A good tool for this is "Hash My Files." Make sure it matches what the website says it should be. If it doesn't, you will have to redownload.
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk

xKroniK13x said:
You never noted that you wanted to recover things. I'd deal with the phone app force quitting and copy things to your computer via the USB. After you get everything you need, try a full wipe. If you don't want to do a re-download of the firmware, at least verify the hashes. A good tool for this is "Hash My Files." Make sure it matches what the website says it should be. If it doesn't, you will have to redownload.
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
Click to expand...
Click to collapse
It's the 2nd comment about that issue. I'm going to need to re-post what I said in my previous post, instead of say "following what I said on my previous post..."
Pedreo1997 said:
Uhm... Good afternoon.
I really don't know what happened to my XT907. I was playing Castle Clash, and then, suddenly...
- Smart Launcher Pro stopped
- GApps stopped
- Messenger stopped
- Amazon MP3 stopped
- WhatsApp stopped
And 4 or 5 more apps stopped. I nned to say what I wasn't using any of that apps but Smart Launcher Pro and WhatsApp.
So I selected the common Power Button... Power Off... Then I used the common Power Button for Turn On my XT907...
Stuck on the boot animation. It makes the sounds as receiving WhatsApp messages and that, but it's eternally on the boot animation (it isn't a bootloop)
What to do in this case?
(I need to add something else: I used the volume up button and every time I use it, the cellphone vibrates)
Click to expand...
Click to collapse

ATTACK said:
You never stated that you couldn't boot to the OS in the OP.
After reading your other post, I believe you have a bad eMMC(?) and your device may be stuck in R/O. If that is the case your phone is non-recoverable. Your only option is to 'try' and restore via RSD or similar - but its unlikely to fix the issue.
Sent from my Moto G™
Click to expand...
Click to collapse
I never wanted to say this but... you're right.
After trying to flash with RSDflasher, HouseOfMoto and RSDLite... I reached nothing. Now, I really don't care now for DCIM and that, I just want to get my cellphone again alive :crying:

Bricked My Lenovo Tab 2 A8-50F and How To Root Samsung Galaxy Tab A 8.0

(Requesting delete on my first post)
I was screwing around with my newly rooted Lenovo Tab 2 A8-50F, specifically with SuperSume. Trying to change king roots crappy SuperSU to the official SuperSU, when it wouldn't boot past the logo, so being the idiot i am. I tried hard resetting it. It wouldn't go past a sliver of the progress. Could anyone give me a tutorial on how to fix my device?
It seems like EVERY tablet I get doesn't have a root strategy. I'm hoping this one does. I found strategies online with broken links, etc. But I am wondering if anyone could give me a tutorial, even though there is already some forums. It is running Marshmallow 6.0.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I attached some info about my device.
Sent from my SM-T350 using XDA-Developers mobile app

SpookehAndroid said:
(Requesting delete on my first post)
I was screwing around with my newly rooted Lenovo Tab 2 A8-50F, specifically with SuperSume. Trying to change king roots crappy SuperSU to the official SuperSU, when it wouldn't boot past the logo, so being the idiot i am. I tried hard resetting it. It wouldn't go past a sliver of the progress. Could anyone give me a tutorial on how to fix my device?
It seems like EVERY tablet I get doesn't have a root strategy. I'm hoping this one does. I found strategies online with broken links, etc. But I am wondering if anyone could give me a tutorial, even though there is already some forums. It is running Marshmallow 6.0.1
View attachment 3825333
I attached some info about my device.
Sent from my SM-T350 using XDA-Developers mobile app
Click to expand...
Click to collapse
http://xda-android-development.blogspot.com/2016/06/lenovo-tab-2-a8-50f-stock-lolipop-rom.html.extract zip and use SP flash tool to flash your lenovo device.If you don't know how to flash rom using SP flash tool then search in Google.And after that you can again root your phone using kingroot.To replace kingroot with Supersu try This instruction.

Røbin said:
http://xda-android-development.blogspot.com/2016/06/lenovo-tab-2-a8-50f-stock-lolipop-rom.html.extract zip and use SP flash tool to flash your lenovo device.If you don't know how to flash rom using SP flash tool then search in Google.And after that you can again root your phone using kingroot.To replace kingroot with Supersu try This instruction.
Click to expand...
Click to collapse
Thanks. Will let you know if it works!
Sent from my SM-T350 using XDA-Developers mobile app

Røbin said:
http://xda-android-development.blogspot.com/2016/06/lenovo-tab-2-a8-50f-stock-lolipop-rom.html.extract zip and use SP flash tool to flash your lenovo device.If you don't know how to flash rom using SP flash tool then search in Google.And after that you can again root your phone using kingroot.To replace kingroot with Supersu try This instruction.
Click to expand...
Click to collapse
I'm actually finding many tutorials on how to flash it. It's quite unclear. Could you tell me how?
Sent from my SM-T350 using XDA-Developers mobile app

SpookehAndroid said:
I'm actually finding many tutorials on how to flash it. It's quite unclear. Could you tell me how?
Sent from my SM-T350 using XDA-Developers mobile app
Click to expand...
Click to collapse
Follow this tutorial.

Røbin said:
Follow this tutorial.
Click to expand...
Click to collapse
Still doing the same thing. I flashed and all.

SpookehAndroid said:
Still doing the same thing. I flashed and all.
Click to expand...
Click to collapse
You flashed your device but didn't boot up?I need some more details to identify your problem.

Røbin said:
You flashed your device but didn't boot up?I need some more details to identify your problem.
Click to expand...
Click to collapse
It still tries to hard reset when I start it up. But it gets stuck
Sent from my SM-T350 using XDA-Developers mobile app

SpookehAndroid said:
It still tries to hard reset when I start it up. But it gets stuck
Sent from my SM-T350 using XDA-Developers mobile app
Click to expand...
Click to collapse
Any encryption error after boot up?If not how did you know it's trying to hard reset the device.Actually I can hardly understand what you are trying to say. I need full details or logs.And how come your device not booting up after flashing the stock rom via sp flash tool.Providing log would be helpful to understand.

Røbin said:
Any encryption error after boot up?If not how did you know it's trying to hard reset the device.Actually I can hardly understand what you are trying to say. I need full details or logs.And how come your device not booting up after flashing the stock rom via sp flash tool.Providing log would be helpful to understand.
Click to expand...
Click to collapse
The tutorial you have me is vague. It does not say which settings to have enabled or disabled
Sent from my SM-T350 using XDA-Developers mobile app

Your method fixed it!!!!!? I wasnt being patient enough
Sent from my SM-T350 using XDA-Developers mobile app

SpookehAndroid said:
The tutorial you have me is vague. It does not say which settings to have enabled or disabled
Sent from my SM-T350 using XDA-Developers mobile app
Click to expand...
Click to collapse
What do you mean "It does not say which settings to have enabled or disabled"?I gave you the right tutorial to flash your device correctly.I didn't say it will enable or disable something.It will just recover your phone from bricked.And by the way you are not explaining much about your device problem.Just tell me what you really want to say.you couldn't flash the device correctly?If you see any error message show me that.

SpookehAndroid said:
(Requesting delete on my first post)
I was screwing around with my newly rooted Lenovo Tab 2 A8-50F, specifically with SuperSume. Trying to change king roots crappy SuperSU to the official SuperSU, when it wouldn't boot past the logo, so being the idiot i am. I tried hard resetting it. It wouldn't go past a sliver of the progress. Could anyone give me a tutorial on how to fix my device?
It seems like EVERY tablet I get doesn't have a root strategy. I'm hoping this one does. I found strategies online with broken links, etc. But I am wondering if anyone could give me a tutorial, even though there is already some forums. It is running Marshmallow 6.0.1
View attachment 3825333
I attached some info about my device.
Sent from my SM-T350 using XDA-Developers mobile app
Click to expand...
Click to collapse
Disclaimer
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research of this topic on your own before you take a look at it. YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you, all, at the same time.
You have been Warned.
Sorry if I am posting so late, but I have successfully rooted the SM-T350 a bunch of times. First of all you will need ODIN and then you will need the TWRP file for SM-T350.
(I chose the Lollipop version of TWRP because it is still compatible with the Marshmallow version of SM-T350 and it also is compatible with 3rd party apps while the Marshmallow version of TWRP is not compatible.)
You will also need SuperSU.
1) Download ODIN (look above for link) and then download TWRP for SM-T350. Also download SuperSU.
2) Before you turn off your Android device, transfer the download SuperSU to your preferred location in the device. Also go to Settings > About Device > Tap on Build Number 7 times until you see the Developer Mode On notification. Then you have to go to Developer Settings and then tick the USB Debugging Mode to on.
3) Open ODIN, plug your device (must be turned off completely) and then press AP in the ODIN application.
4) Locate the .tar5/.tar file of TWRP and select it (open it for ODIN).
5) Go back to your device and then go to Download Mode (Volume Down + Power Button + Home Button).
6) ODIN will say "Device Added!"
7) That's when you press Start in ODIN and then your custom recovery should be installing.
8) When it says finished, unplug your device from the computer and then your device should reboot.
9) After rebooting, turn off your device again and then go to Recovery Mode (Volume Up + Power Button + Home Button)
10) Locate the SuperSU .zip file and flash it through TWRP!
Happy Flashing!
-ParadoXGodzillA

No os on phone

That is the message I get in TWRP when I try to reboot. Pretty sure it was Format Data I selected in order to change encryption. I made multiple backups prior to performing the format option. Restore has nothing. I hope there is a solution. Downloading a ROM now on computer right now . Ill keep my phone in recovery and plugged in. I tried to put off posting . Thanks for any help. Instructions here are great I tried taking time and read a ton before taking the plunge. Phone is a Nexus 6 got through everything up to picking a ROM. I probably should have gone to that thread just thought a few more folks would see it here. Watching newbs mess up.

Have you tried returning it back to stock? Flashing the factory image to of the original OS. And yea, read and pay attention because you don't wanna have a paper weight
Sent from my Pixel 2 XL using Tapatalk

bluizzo said:
Have you tried returning it back to stock? Flashing the factory image to of the original OS. And yea, read and pay attention because you don't wanna have a paper weight
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
well after more research I found I can do that . I will have to know the exact one apparently. this is a link for stock images https://developers.google.com/android/images
I have a new rom. to instal original is the same process so i want to try the rom. unless thats a bad idea. either way im stuck at the finish line.
trying to sideload ROM . do i have zipfile in wrong place?
do I have to reboot in recovery?
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools> adb devices
List of devices attached
ZX1G22QGDZ recovery
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools> adb sideload PixelDustROM-pie-caf-marlin-20190519-0024.zip
* cannot read 'PixelDustROM-pie-caf-marlin-20190519-0024.zip' *
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools> adb sideload PixelDustROM-pie-caf-marlin-20190519-0024
* cannot read 'PixelDustROM-pie-caf-marlin-20190519-0024' *
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools> adb sideload Desktop\Nexus6\PixelDustROM-pie-caf-marlin-20190519-0024
* cannot read 'Desktop\Nexus6\PixelDustROM-pie-caf-marlin-20190519-0024' *
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools> adb sideload PixelDustROM-pie-caf-marlin-20190519-0024
* cannot read 'PixelDustROM-pie-caf-marlin-20190519-0024' *
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools> adb sideload PixelDustROM-pie-caf-marlin-20190519-0024.zip
error: closed
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools> adb sideload PixelDustROM-pie-caf-marlin-20190519-0024.zip
error: closed
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools>

are you sure you have the right ROM it looks like you might be trying to flash a Pixel XL rom.
are you in the right forum?

Mikejusmc said:
well after more research I found I can do that . I will have to know the exact one apparently. this is a link for stock images https://developers.google.com/android/images
I have a new rom. to instal original is the same process so i want to try the rom. unless thats a bad idea. either way im stuck at the finish line.
trying to sideload ROM . do i have zipfile in wrong place?
do I have to reboot in recovery?
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools> adb devices
List of devices attached
ZX1G22QGDZ recovery
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools> adb sideload PixelDustROM-pie-caf-marlin-20190519-0024.zip
* cannot read 'PixelDustROM-pie-caf-marlin-20190519-0024.zip' *
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools> adb sideload PixelDustROM-pie-caf-marlin-20190519-0024
* cannot read 'PixelDustROM-pie-caf-marlin-20190519-0024' *
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools> adb sideload Desktop\Nexus6\PixelDustROM-pie-caf-marlin-20190519-0024
* cannot read 'Desktop\Nexus6\PixelDustROM-pie-caf-marlin-20190519-0024' *
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools> adb sideload PixelDustROM-pie-caf-marlin-20190519-0024
* cannot read 'PixelDustROM-pie-caf-marlin-20190519-0024' *
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools> adb sideload PixelDustROM-pie-caf-marlin-20190519-0024.zip
error: closed
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools> adb sideload PixelDustROM-pie-caf-marlin-20190519-0024.zip
error: closed
PS C:\Users\Owner\Desktop\platform-tools_r28.0.3-windows\platform-tools>
Click to expand...
Click to collapse
That explains a lot. Wrong device. Are you the Nexus 6(aka Shamu) or are you using the Pixel xl(aka Marlin). The link to the factory image tells you the code names for the device. I provided a screen shot of the factory image page that shows you the Nexus 6 images. Last imag will be 7.1.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 2 XL using Tapatalk

bluizzo said:
That explains a lot. Wrong device. Are you the Nexus 6(aka Shamu) or are you using the Pixel xl(aka Marlin). The link to the factory image tells you the code names for the device. I provided a screen shot of the factory image page that shows you the Nexus 6 images. Last imag will be 7.1.1View attachment 4767213
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
well shi*
Thanks for the heads up ill go get new images. unfortunately i have another issue. I keep getting told adb isnt the updated version and im sick of looking for one . i even dl the whole android studio to see what it may have for me.
could the fallowing work:
lineage-16.0-20190515-nightly-shamu-signed

bluizzo said:
That explains a lot. Wrong device. Are you the Nexus 6(aka Shamu) or are you using the Pixel xl(aka Marlin). The link to the factory image tells you the code names for the device. I provided a screen shot of the factory image page that shows you the Nexus 6 images. Last imag will be 7.1.1View attachment 4767213
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
also the stock images i still not sure which i need

Mikejusmc said:
also the stock images i still not sure which i need
Click to expand...
Click to collapse
For abd you can get it if you download android studio. Would also suggest a toolkit but in a way I'd suggest you try to do it without the toolkit. And factory image you can use any or use the latest
You can use lineage but do the rooting process from scratch. Go stock and root from there.
Sent from my Pixel 2 XL using Tapatalk

bluizzo said:
That explains a lot. Wrong device. Are you the Nexus 6(aka Shamu) or are you using the Pixel xl(aka Marlin). The link to the factory image tells you the code names for the device. I provided a screen shot of the factory image page that shows you the Nexus 6 images. Last imag will be 7.1.1View attachment 4767213
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
bluizzo said:
For abd you can get it if you download android studio. Would also suggest a toolkit but in a way I'd suggest you try to do it without the toolkit. And factory image you can use any or use the latest
You can use lineage but do the rooting process from scratch. Go stock and root from there.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
So I've been fumbling around in twrp. I was going through all the files when I came across one that looked similar to what my computer was displaying when connected. It was it for sure put the lineage in the file and it appeared in the twrp file. ill probably still go back to stock or atleast have it on hand for my next blunder. Thanks for the help ! stay alert I'll be back im sure,

bluizzo said:
For abd you can get it if you download android studio.
Click to expand...
Click to collapse
Just to point out that it's no longer necessary to download the whole of Android Studio just to get ADB and Fastboot. See here for details. Then, do what I do and use the binaries to update the install of Minimal ADB and Fastboot (mentioned at the link).

OP are you sorted? Hope so.
I like happy results for XDA members.

It took me a couple trys and reboot. Put lineage 16 ,latest twrp, and gapps 9. That's what works for me. I used adb and fast boot to sideload.