Related
Hey Guys,
So I have been all threw the forum over the past week plus trying to find a solutions and have tried the majority of the ones on the site. Here is what happend:
HOW I GOT HERE:
I was running a CM10 nightly build from 01/15/2013 that was installed via CWM. I had been running it for about a week. When I went to bed I set my phone on the nightstand. About 2 hours into sleep the phone rebooted as I eventually woke up and noticed it thinking it was just the phone wonking out. When I up fully 6 hours later the phone was still rebooting. Since then when ever I cut on the phone it will no get passed the Google logo with the padlock. I can boot into fastboot and recovery. I am running the latest CWM 6.0.2.5.
PHONE VITALS QUICK GLANCE
Android ROM version: CM10 01/15/2013 Nightly Build
Baseband: D720SPRLC1
Bootloader: D720SPRKC5
Recovery: CWM v6.0.2.5
WHAT I HAVE TRIED
Restoring from backup
My first fix was to flash three different roms via recovery (doing full wipes each time)
Then I tried flashing a new recovery
Formatting /system, /cache, /data, and /boot and then flashing a new rom
Then I focused on trying to get the USB storage to mount so I tried using adb shell to repair the file system and that worked
Then I tried new roms and things got REALLY weird. When I would place a rom on “sdcard” it would be available to flash. When I flashed it though it would not take and upon returning to recovery it wouldn’t be there or when I mounted the storage again. After about 10 times of this I figured let me make sure I am not crazy and try the following.
Format the internal storage. In windows when I tried this windows would show that the device formatted and was empty one I dismounted after putting items on it and go back to storage by both remounting it or by recovery the old data would come right back. In Ubuntu when I tried formatting it both via disc recovery and gparted they both said the device was empty but that they were unable to create a partition.
So then I went down the path of all of the debricking tools out there including the one from AdamOutler's (I think it is called ressurector), ODIN, and the Nexus Root Tool all with varying results.
Ressurector kept saying injection failed
ODIN just does not work on the nexus s from what I can tell (spent a day researching and no one seems to give a definitive answer on this one)
And Nexus Root Tool attempts to flash back to stock but runs into an error with the baseband.
So next I decided to try and flash back to stock using the Google images. Using Ubuntu I ran the flash-all.sh that comes in the zip and kept running into the baseband issue.
So next I found OldBlue910’s post with all the OTA updates and I went after trying to use that to fix my phone. Thanks to the amount of instruction he gives I got a lot further and got the flash-all.sh in his stock zip to give me a better error message telling me which baseband I needed to have to go back to stock which when I double checked he includes in the zip. The problem is when I try to flash that radio fastboot tells me I was successful but the bootloader still reads as D720SPRLC1 and does not change regardless of what I do. When I try flashing the stock images again after flashing the radio I receive the same errors.
So now I think I have hit the real brick wall and unless someone has any advice I will need to go and buy a new phone. Hoping you guys can help. I figured if you guys can figure out a hard brick then this is still doable, I have just exhausted my own realm of knowledge.
Please and thank you’s to anyone with advice.
Could you get any lights ON? The buttons or the screen?
lights are on
Yes during the boot loop the Google logo comes up, then the screen goes black, then the Google logo comes back, and finally in about 20 seconds the lights come on. Once that happens after about 4 minutes the process starts all over again.
Hi!
My P500 was originally Gingerbread 2.3.3, than I used CM 7.2 with AmonRa 3.0.6 recovery for a year.
So I tried to flash KitKat (http://forum.xda-developers.com/showthread.php?t=2589303), and got some issues.
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Whatever I choose, I got that black screen with
"fastboot mode started
udc_start()".
Thaaaan, I see this: http://forum.xda-developers.com/showthread.php?t=2439466
and tried to downgrade SU to v1.55. But the CWM got an error, and cannot install (even with AmonRa)...
After all, I can't get KitKat working, and got back to AmonRa recovery and CM 7.2.
To complete the "good vibe", my Android can't get AT ALL connect through USB, so I can't test any ADB command.
I don't know where I'm doing wrong... Any directions??
Thanks!!!!
SOS
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.
LonerPrime said:
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.
Click to expand...
Click to collapse
The way back home without buggy LG Mobile anything: Remove and replace batter, press home, volume-down and power keys simultaneously. Can be a bit tricky but will get you back in recovery. I assume you did that backup before playing. Restore it to get the phone back up.
Two ways to get your Kitkat:
1. Using the Version-8 install, do a clean install and be sure to choose an item in the various menu panes. Should work with this and then you need to reinstall and setup everything.
2. Take the "nightly" and install normally doing the requesite steps in the backup.
Thank you, but– Nvm fixed it.
@Dovidhalevi
Thank you for your amazing advice. I was able to get into recovery and restore from my nandroid backup. *Thank god I did that*
But kittkat ROM is still being a pain. I decided to read the logs of version 8 of the ROM a bit more closely and found this:
Upgrading from CM-10.2 or older / Fresh (First time) Installation: Now DON'T WIPE ANYTHING (Data/Factory reset, Wipe Cache partition, Dalvik Cache, Format System) everything have built in Aroma Installer. Simply flash through sdcard or adb sideload, Follow the Aroma Menu. Finish and Reboot device. Avoid Facebook, Whatsapp, Viber, Hangout apps while selecting apps to be flash, it may gives you fastboot mode. Done!!!
I decided to try my luck once more and disabled all those apps during the installation. But just before rebooting my phone lost root access again and asked if I wanted to fix it or not and then it froze again on LG logo afterwards. Another force restart and it went straight into fastboot mode. Had to do another restore to get my phone working on the older backup.
Now I know it isn't the CWD cause I am running that with my older Cynogen 7.2 OS and its rebooting without a hitch unlike kittkat which mysteriously loses root access...
I really apologize if I am being a bit noobish. Even though hardware/networking/linux[Red Hat] is like playing in my backyard, android itself is a new concept to me, hence I really appreciate all the help I can get on this to work.
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime
I'll try
LonerPrime said:
@Dovidhalevi
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime
Click to expand...
Click to collapse
Glad you fixed your phone!! I forgot to say what I did to "fix" it...
Read error... maybe???
I'll try as soon as I get home, with results!! Thanks!!!
I did that... =/
yes.. i was doing right. All the 6 times I tried...
And tried again now, just to be sure, and FASTBOOT again.
=/
jpesci said:
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Click to expand...
Click to collapse
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.
It's fixed, but no Kitkat...
shinobisoft said:
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.
Click to expand...
Click to collapse
Oh, sorry. Maybe bad explanation. I did get it fixed. All the "x" times, heheh =)
I just got in recovery by pressing home+vol up+power, and flashed back my older ROM. Now I'm trying CM 10 by Jenkins.
The problem isn't the "fastboot" message itself... but don't get Kitkat working =/
But thanks for the reply anyway!
kitkat by mukulsoni... ui stops with multiple popupd
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..
amit2411 said:
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..
Click to expand...
Click to collapse
Boot in to your recovery and try wiping your cache and dalvik cache.
still no working
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes.
shinobisoft said:
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes.
Click to expand...
Click to collapse
Thanks for explanation!! But... still nothing.
I did EVERY SINGLE STEP like you said. Except for baseband, cause my phone was originally 2.3.3. But all new downloads...
After flashing, try to reboot... DAMN! "root access possibly lost..." YES/NO, gives me same problem. I read another thread about this erros, people said about SU. Can it be? I tried to flash another SU version, but CWM return an error too =/
jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559363 try this.
voltaire23 said:
http://forum.xda-developers.com/showthread.php?t=2559363 try this.
Click to expand...
Click to collapse
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)
jpesci said:
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)
Click to expand...
Click to collapse
I am considering the jenkins build from here: http://download.androidarmv6.org/_builds/
can anyone help with finding the smallest gapps that will fit?
Edit:No need
I have a Asus TF700T and while it was in my car in its case it apparently started on it's own and ran down a full charge to about 10% so it must have been going for hours which would explain why it got so warm. I could not shut it off so it stayed on until there was no more charge. I was then able to charge it. When I hit the start button it starts but just hangs up in the animated boot screen and goes no further. Then I tried the on button with the volume button and got into TWRP. I really don't know anything about TWRP but I looked around and tried rebooting and a few other options but nothing changed. Still stuck on the boot up screen.
So I'm willing to learn about my tablet now that I am forced too. Can anyone please point me to the right solutions and can anyone tell me why it started on its own? You help is much appreciated. Thanks.
More likely some app never shut down and got hung up, running the battery down. Unless you live in Phoenix and had in your car in full sun heating it up to 140 F...
To give you any advice worth a damn you need to provide:
bootloader version
TWRP version
what rom you are running
In lieu of that, and to possibly get the tab out of the stuck boot, you could just do a factory wipe in TWRP.
Choose the Wipe option and swipe the button - let it finish and reboot system. That will wipe all user installed apps and settings, but leave your personal files untouched.
Let us know where that got you.
For general info and to get your PC set up for fastboot/adb you could peruse my guide here: http://forum.xda-developers.com/showthread.php?t=2688891
Thanks for the info. I will charge it back up and try your wipe suggestion.
As far as the other info you need, I'm not sure how I can get that if it won't boot, except probably the TWRP version. Can you suggest a way to obtain that info. As far as what Android version I was using I'm not really sure about that either. I bought this used in early 2013 and the version was whatever was around back then. Geez, I'm a little embassased. It's my most important tool and I know nothing about it. It's as if you asked me my sons name, age, and birthdate and I couldn't tell you. Back when I used a desktop, I knew everything about it but now, shame on me.
The TWRP version would help somewhat. Assuming you have a TWRP version compatible with your bootloader it would give us a hint on what you were running. But if you can boot to the bootloader with Power and Volume Down, just read the tiny script. Your BL version is right there.
But if TWRP is still working you could use it's build-in file manager to copy all your data off internal storage to a microSD.
Then download the latest firmware from Asus, unzip the file once, resulting in another zip and place that zip on a fat32 formatted microSD.
Flash the firmware in TWRP.
That would get you onto the latest bootloader, but would also install the stock recovery and rom.
Next just decide which custom rom you want to run, find the correct TWRP version, flash it in fastboot and then flash the rom.
Who would of thought that a menu option called "Wipe" would get me back up and running? Seems to me that Wipe would just blow away everything. You assistence is greatly appreciated.
Fogot to mention that I,m also going to follow your suggestions with the lastest firmware and custom rom but I have to put that is on hold until I have a backup tablet so I can continue doing my Ebay work and learning more on this terrific website. Thanks again for your help.
I'll give you the whole story so bear with me. First off, I'm very new to the Android OS and tinkering with phones and tabs. I'm a computer network administrator and pc mechanic. I'm mainly a hardware guy though, no programming experience at all. But I'm not afraid to jump right into the inner workings though, especially if it's already broken.
And that's probably why I find myself in this position today with this device.
I recently bought this Tab 7.7 to use as a display for my new drone. When it arrived I tried to download the flight control app and it refused to install. No error messages, it just did not install. In looking, the unit was on Honeycomb 3.0. My guess was it was WAY behind in upgrades so off I went to make it bigger and better. I downloaded a zip file for Lollipop 5.1 onto my SD card and was able to load that. Upon reboot I had a screen and an OS. I went into settings and saw where it had upgraded. Success, right? Well, then I went into Wi-Fi settings to add my network. The keyboard would not come up on screen. So I did a bit more research and tripped over the fact that I needed to also load a GAPPS file to add the apps and drivers back. THAT is when I went down the rabbit hole.
The install did not go well and I somehow wound up with no OS at all. Probably after thinking I was following the correct process of resetting and clearing caches before installing the new files. Then this 3 day journey of learning began. I have downloaded Odin, Notepad++ to edit files, Minimal ADB and Fastboot, Samsung KIES and all manners of ROM builds and GAPP files. As of this moment I have absolutely no OS on the unit. Upon turn on it goes directly into the CWM Recovery v6.0.4.5 screen. I am able to boot it to the download screen and Odin can SEE the unit. But I can't get any further with that program other than seeing the unit listed as detected. I'm not able to get anywhere with KIES. No detection or anything.
Now I'm admitting I messed this unit up. I'm not blaming any written procedure or ROM developer. I'm not stupid but evidently don't know all I NEED to know about this process. So I'm here asking for guidance. I really would like to revive this unit and get it back to where I can use it as my monitor as originally planned. But one step at a time. Please give me the correct steps to do to get an OS reloaded and revive this unit.
I'm thinking that my best bet would be to use a TWRP image file to rebuild it. But I need the step by step process for that to make sure I do it correctly.
MANY thanks for this board and the help AOT!!!
Dave
Being the impatient type as well as a DIY'er, I pressed on with trying to revive it myself. I downloaded TWRP as a zip file and added it to the SD card. Booted and installed from the zip file. Screen said it loaded successfully. I rebooted and tried going into recovery (holding power and volume up) expecting it to go into the TWRP console. Instead it went into the regular CWM Recovery screen. Oh well, another frustrating dead end for me. I'll just set it aside until I get some good instructions from someone that knows what they're doing. Best I do that rather than brick it. I can at least access the recovery screen. Odin sees the unit but I cannot find the right file to load from there.
Okay, I'm truly stopping now. Another dead end. I was able to find a couple of files for restore using Odin. Loaded one and now I boot into Android system recovery <3a> instead of the CWM Recovery screen as before. I tried loading a recovery image from a zip file and it failed signature. That seemed to be telling me the tab is now not rooted. So I downloaded SuperSU to the SD card and tried to load it. No joy, it fails signature too.
Arrrggghhhh.........
Can't even shut it down.
Told you I'm impatient. Now have used Odin and installed TWRP 3.0.2-0. Going slowly now. Taking it one step at a time. This is the first positive step I've had so far in 3 days.
:silly:
Baby steps. LOL
Used TWRP to flash SuperSU. Now the unit is rooted and rebooted to TWRP. I still have no OS on there as of yet. I'm guessing my next step is finding a good stable ROM file and use TWRP to flash onto the tab.
Downloaded OmniROM Marshmallow 6.0.1 (https://androidfilehost.com/?w=file...69dc16313bf0332c8794621c6c7f505edf855e0d499d8) and the Open GApps ARM 6.0 stock file (http://opengapps.org/).
Will try to flash those through TWRP and hope for the best.
Joy...at last. The downloaded OMNI 6.0.1 worked when loaded using TWRP. The GApp file failed. Will try another one to see if it works.
https://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Booted to TWRP and was going to install the GApps file. I had left OMNI 6.0.1 on the card too and by mistake selected it. Dooohhh......
I'm an accident waiting for a place to happen. LOL
So, after REloading Android 6.0 I proceeded to load the gapps base file. Reboot and all appears to be going smooth. Apps updating and such. After about 2 minutes I get a message onscreen that unfortunately setup wizard has stopped. Hit okay but the message persists to pop up.
So.....
I guess I'll take a short break then do a wipe and reload of the OMNI and the working gap file and see what happens. At least I got to see it actually boot and let me get into setup. I went to add my Wi-Fi network, added the credentials but it never connected. Something else to look into.
More fun ahead....but at least I'm moving forward now.
A happy camper. Because I was able to revive this tab and because I had the patience to figure it out myself. And my wife swears I have no patience.
LOL
So...the key was downloading Odin and the Samsung drivers on my laptop.
Then download the TWRP.tar file to the laptop.
Boot the tab into download mode by holding power and volume down button. Select yes to continue.
Connect the tab to the laptop with the USB cable. See that Odin can communicate with the tab.
Select AP and find the TWRP file location and start. After it finished, rebooted and since there was no OS installed, TWRP recovery opened.
The next thing was download SuperSU file and drop it onto the SD card. You CAN go ahead and find the correct ROM you want and download the file as well as the GApp file. Drop all 3 onto the SD card.
Then insert it into the tab and select Install. Just be very observant WHICH file you load in what order.
You will need to install the SuperSU, reboot and then install the OS ROM followed by the GApp file.
Select SD card and the SuperSU file. Wait for it to complete then reboot.
After loading SuperSU and reboot, you need to get back into TWRP Recovery program by rebooting while holding power and volume up. This time when you select Install, pick the ROM file first then pick additional files and select the GApp. This way TWRP will first install the OS from the ROM file and immediately load the apps file. Then reboot and you are done!!!
And it took 3 days of round about to figure this out.
LOL
I just downloaded my flight control app and I'm off and running with Marshmallow.
Hope this helps at least one person that is new to this whole process as I was!!!
Dave
Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.
J727P
Nupid Stoob said:
Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.
Click to expand...
Click to collapse
ok you have an older phone the J700P you can start by downloading odin an twrp recovery an superSU zip you can get twrp from here !https://twrp.me/devices/samsunggalaxyj72015qcomsprint.html
an odin from here
https://mega.nz/#!nYVDXBAC!_cTWbW4_Ow8sZMWcZvO7bVwEEBFlD1DQsB5NeFhj1EY
An just google latest superSU zip to find that !
good luck !
step 1 enable oem in development settings !
step 2 put phone into download mod an flash twrp then boot into twrp recovery an flash superSU zip !
Thank you for the info. I'm presently confused. Here's what I've done:
I ran Odin and flashed with twrp-3.2.1-0-j7ltespr.img.tar. It went through successfully going off odin's message.
Vol. up + home + power. It'll eventually show a yellow triangle with the white trash can guy on it's side stating "No Command". Power + up gets the Android Recovery screen.
At this point, am I supposed to choose the Wipe Data/factory reset option? I see tuts that seem suggest I should already be in the twrp UI or something. I've tried watching vids and looking at a handful of tuts, but either they are the wrong phone, too old, the button combos show something else entirely, etc.
Thanks!
Anyone? Videos show the buttons vol. up + home + power as booting right into twrp recovery gui. For me, it's going into "Android Recovery" screen. Is there an extra step with Odin or something that I missed? Or am I supposed to wipe/boot in the Android Recovery screen and it'll boot the twrp recovery gui? If bricking something I'm not familiar with wasn't a concern, I'd be courageous with it.
I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?
J700P
Nupid Stoob said:
I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?
Click to expand...
Click to collapse
Ok when flashing twrp with Odin first uncheck auto reboot in options flash twrp pull battery replace battery an boot into twrp an flash superSU zip then reboot system !
Thank you so much Peter! That did the trick THANK YOU :good:
For posterity to anyone else w/limited root knowledge with a SM-J700P Virgin variant running 7.1.1 (and what was most recent factory updates until this point); Flashed the twrp-3.2.1-0-j7ltespr.img.tar again w/o auto reboot in options of Odin, pulled battery once safe (i.e. you get the "Pass" message from Odin confirming everything went as planned) to get out of the downloading screen, replaced battery, booted the recovery (vol up + power + home) and it finally booted into the twrp recovery gui. Selected the "Install" option, then went to where the supersu.zip was stored on the SD (I created a separate "supersu" folder via PC connection for easy locating; internal phone memory card looks to now be unlocked, so can most likely use that if you don't have a SD card). Checked the "reboot once installed option" in the gui box and swiped to install supersu,zip and verified it was rooted via app after phone fully booted back up.
BTW, If anyone gets a hang/crash in Odin immediately after trying to select a twrp tar image in the "AP" box, try downloading the twrp image via PC instead of the through the phone (the legit twrp site that has the repository of past/current .tar), and just put it somewhere like Odin folder on desktop. Somehow, mine were getting corrupted via phone download through the twrp app, and Odin would NOT recognize the file was bad/corrupt when trying to select it via the AP box and hangs instead of giving a warning message. I ran into this earlier on then noticed the file was too small for some reason after viewing it on my PC, hence the Odin hang that needed a task manager kill.
I hate to necro an old thread but I still do not want to create an entire new topic for a single question. If I was to follow this info will it wipe the phone or will it simply root it while keeping all data on the phone? I ask as it is my wife's old phone and she would be pissed if I wiped her apps and everything on accident since she wont be able to remember what she had.
Edit: also when I add the TWRP file to odin it immediately hang/crashes like OP mentions but I am already DLing via pc. any thoughts?