Related
So I updated to the .28 update this morning, and it all went good. then it got to the stage of booting up, and it doesnt go any farther than the Asus logo with the spinning wheel underneath. I tried doing a reboot by holding the power button but nothing helps. I am rooted on the .21 update and not unlocked. Anyone help? I dont want to have to RMA. Thank you so much in advance!
Gabewalters said:
So I updated to the .28 update this morning, and it all went good. then it got to the stage of booting up, and it doesnt go any farther than the Asus logo with the spinning wheel underneath. I tried doing a reboot by holding the power button but nothing helps. I am rooted on the .21 update and not unlocked. Anyone help? I dont want to have to RMA. Thank you so much in advance!
Click to expand...
Click to collapse
Try hitting the factory reset or use one of the brick fixes detailed in the dev section stickies.
By chance had you modified any system files or were you bone stock with just root access? i ask this because i upgraded to .28 with no problems with root.
shreddintyres said:
Try hitting the factory reset or use one of the brick fixes detailed in the dev section stickies.
By chance had you modified any system files or were you bone stock with just root access? i ask this because i upgraded to .28 with no problems with root.
Click to expand...
Click to collapse
I have only edited one /system/app file and it was to paste the Svoice app to see if it would work. I am pretty sure I deleted it though. Would this be why? And what do you mean by hitting the factory reset?
I am in the same boat the update killed My Prime.
I tried the volume down restart no luck gets stuck on ASUS logo
I tried the Volume down and delete user data and restart no luck gets stuck on ASUS logo
any help
tkdsl said:
I am in the same boat the update killed My Prime.
I tried the volume down restart no luck gets stuck on ASUS logo
I tried the Volume down and delete user data and restart no luck gets stuck on ASUS logo
any help
Click to expand...
Click to collapse
I am glad Im not the only one. I know how you feel! I hope we can get this thing back up and running. :-|
I checked the Sticky on the Dev Section and they don't cover this type of damage.
This means I have to send my prime to ASUS. dang it.
Guys, the update didn't brick your Primes, sometimes fooling around with the system files can have a negative effect. If the update was no good, ALL of our Primes would be bricked, not just some.
Good luck though!
Gabewalters said:
I am glad Im not the only one. I know how you feel! I hope we can get this thing back up and running. :-|
Click to expand...
Click to collapse
I tried restarting with the recovery kernel and I get an android logo laying down with red exclamation mark. not sure what that means how to fix that yet.
---------- Post added at 11:52 AM ---------- Previous post was at 11:44 AM ----------
MRCANNADY said:
Guys, the update didn't brick your Primes, sometimes fooling around with the system files can have a negative effect. If the update was no good, ALL of our Primes would be bricked, not just some.
Good luck though!
Click to expand...
Click to collapse
the only thing is, I did not change system files on my prime, I kept it stock. and I have received updates and updated them before. I just found out that the repair center for ASUS in Los Angeles does not service Primes.
The update may have bricked your prime. Although updates succeed with some devices they can fail with others. There is a long history of such issues across platforms.
Sent from my Transformer Prime TF201 using Tapatalk 2
try a hard reset.... insert a paperclip into the hole by the SD card to reset.
If not ping Gary Key or the other Rep, I forget the name and see if they can have an Asus tech offer some other solution. If not RMA it is..
just dont say its rooted
good luck!
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
sledgie said:
I just wanted to have a little post for those of you like me that may have tried updating after downloading the .28 OTA update, then the Prime freezing on the Asus Splash Screen and not rebooting...I found the solution after finally downloading the update this morning from Asus' TW site.
I only have the Prime as my computer and I have an Android phone. No PC for me - was going to try to use a friends last night to get into ADB but it just wasn't happening.
So for me - this is what I had to do.
If after your prime reboots you are still stuck on your asus splash screen, and nothing will get it to boot up - do this:
You must know your Prime's version of the update.
Goto ftp://ftp.asus.com.tw/pub/ASUS/EeePAD/TF201/ or check cky2000's thread right here
forum.xda-developers.com/showthread.php?t=1429873
Download the **COMPATIBLE** update of .28 (I tried .21 plenty of times - .21 would not update my Prime)
If on an Android phone (like I was) goto ES File Explorer and open the **UpdateLauncher.zip file
It should say something like **_epad-user.9.4.2.28.zip
Extract the file to the root directory of your microSD card
Now, goto your microSD card
rename the **_epad-user.9.4.2.28.zip to
EP201_SDUPDATE
**don't rewrite the extension so that it's EP201_SDUPDATE.zip.zip, ES File explorer will only allow you to rename the name, not file extension**
You should now have EP201_SDUPDATE.zip on your microsd
**make sure you charged your prime at least 30 min if it turned off previously**
Put microsd in your Prime
Hold the Volume Down button and the Power Button until it resets and something is written at the top asking if you want to boot into a certain mode press volume up.
Immediately press Volume Up. Make sure Microsd with EP201_UPDATE.zip is in Prime.
It will start to switch to the Android Operating Mode screen with the Android lying sideways with some nuclear fission animation going on.
Blue status bar should start within 3 minutes.
Reboot and rewrite should take approximately 5-10 minutes. When done, your About should show .28 update. Hope this helps anyone who was in the same boat as me. I believe my Prime was bricked a certain way - not sure how.
Click to expand...
Click to collapse
Sent from my VS910 4G using Tapatalk 2
I had the same problem. My Prime is on its way to Asus. Does anyone know what their procedure in these cases? Do they reinstall the system and ship the tablet back or is there more to it? I take it this is all under warranty since the tablets were not unlocked?
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I don't need it, but it's nice to know with stock recovery. I thought recovery was just missing.
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks! I had same issue, just fixed it using this guide! Many thanks to author too!
It's Alive and thank you again for the post and the link, I was really worried about the
If anyone else runs across this thread, you guys don't give up so early. If your prime shows a sign of power, it's fixable without the prime leaving your house.
Congratulations to the guys who are now back up and running. That's amazing. I know how scary that can be to brick an expensive device.
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
Dont you need to have to be unlocked to be able to install .zips from recovery?
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
I dont know what you mean by downloading the compatible version for my prime. Mind helping me out?
Gabewalters said:
I dont know what you mean by downloading the compatible version for my prime. Mind helping me out?
Click to expand...
Click to collapse
He likely means make sure you download the proper sku version. For example, if you have a u.s. prime, can be seen in settings and about tablet info, then you need to download the version for u.s. primes. If you ww. Then you need to download version for ww. If you De. Version, then you need to download De version for your prime.
So I downloaded the right version but when you unzip it, you get a folder, not another zip file. Any help?
EDIT: Figured it out. Apparently unzipping and then moving to the sd card isnt the same as moving to the sd card and unzipping.
@Chainfire has released his CF-Auto-Root for the SM-G900T (T-Mobile US) Galaxy S 5.
I take no credit whatsoever for this, just posting a link to his main thread for all to see.
Please go and thank Chainfire!
With this root accomplished, we can confirm that the T-Mobile bootloader is UNLOCKED.
ROMS/Kernels/Recovery will soon follow from our awesome devs here on XDA.
Link to CF-Auto-Root Main Thread(Multi-variants)
THIS WILL TRIP KNOX COUNTER TO 0x1
ODIN Instructions - Copied from Main CF thread
Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
Click to expand...
Click to collapse
Download links taken from main thread:
SM-G900T (T-Mobile US): CF-Auto-Root-kltetmo-kltetmo-smg900t.zip
Other models
CF-Auto-Root is not yet available for all models - one stock firmwares for these models become available, let me know, and I'll make the corresponding CF-Auto-Roots.
Click to expand...
Click to collapse
Good stuff, downloaded the zip, just waiting for my device to get here....we have to run the update the Kies first, right? Also, any word about CWM or TWRP? They've already made recoveries for the international versions.
stevew84 said:
Good stuff, downloaded the zip, just waiting for my device to get here....we have to run the update the Kies first, right? Also, any word about CWM or TWRP? They've already made recoveries for the international versions.
Click to expand...
Click to collapse
You can run the auto-root on both the updated version from kies, or straight outta the box.
I am trying to get in touch with the developers about TWRP and CWM, but I am sure they are busy trying to get all variants working.
I wouldn't Odin the international TWRP or CWM though. I would wait for a version for us.
idtheftvictim said:
You can run the auto-root on both the updated version from kies, or straight outta the box.
I am trying to get in touch with the developers about TWRP and CWM, but I am sure they are busy trying to get all variants working.
I wouldn't Odin the international TWRP or CWM though. I would wait for a version for us.
Click to expand...
Click to collapse
For sure, I don't want to brick the damn thing. Luckily I've been here before!
ill wait for a none trip counter version or triangle away to come out. should be to long.
khshapiro said:
ill wait for a none trip counter version or triangle away to come out. should be to long.
Click to expand...
Click to collapse
I wouldn't count on it. at least the Triangle away...Knox still hasn't been figured out for previous devices on how to reset it, so I wouldn't count on it for this device. As for getting root without tripping knox, Maybe kingo will update, or root-de-la-vega....who knows at this point.
khshapiro said:
ill wait for a none trip counter version or triangle away to come out. should be to long.
Click to expand...
Click to collapse
There basically won't be a way of resetting Knox.
Because of it being more a hardware flag, once it is tripped it is not reversible.
There might eventually be a way to do it without tripping it, but I wouldn't expect that for a while.
Got my S5 and ran the CFAuto worked like a champ... Rooted in 30 seconds.. Yes it tripped Knox but I really don't care.
Sent from my SM-G900T using XDA Premium 4 mobile app
Come ooonnnnn customer recoveries!
Edit: This is such great news, I'll be buying this version and unlock it to use it on T-Mobile.
Sent from my Nexus 7 using Tapatalk
tankmurdock said:
Got my S5 and ran the CFAuto worked like a champ... Rooted in 30 seconds.. Yes it tripped Knox but I really don't care.
Sent from my SM-G900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Now just to see if WiFi tether for root users works.
He he
And Y_E_S tethering works like a chiz-amp!
Sent from my SM-G900T using XDA Premium 4 mobile app
Since we have root, does that mean 100% that we can flash recoveries and ROMS? Both TW and AOSP?
Worked perfectly.
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
stevew84 said:
Since we have root, does that mean 100% that we can flash recoveries and ROMS? Both TW and AOSP?
Click to expand...
Click to collapse
Yes, though root has nothing to do with this. The bootloader is unlocked, which is why root was obtainable via Chainfire's custom recovery. We have no restrictions on flashing custom ROMs/kernels/recoveries/etc.
I may start working on a custom TW kernel myself once Samsung uploads the source...
zaventh said:
Worked perfectly.
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
Yes, though root has nothing to do with this. The bootloader is unlocked, which is why root was obtainable via Chainfire's custom recovery. We have no restrictions on flashing custom ROMs/kernels/recoveries/etc.
I may start working on a custom TW kernel myself once Samsung uploads the source...
Click to expand...
Click to collapse
Wait, CF custom recovery has nothing to do with root? I thought that was the point of CF "autoroot", am I missing something?
TheArtiszan said:
Now just to see if WiFi tether for root users works.
He he
Click to expand...
Click to collapse
Do u have a link to this?
Sent from my SM-G900T using XDA Premium 4 mobile app
Tmo warranty
Hi,
I'm debating if I should upgrade to SGS5, now that we can root the phone.
Does anyone knows for sure that a tripped Knox means no warranty with T-mo? I'm under the Jump plan and the idea is that I will be able to have warranty on the device if something happens to it (and I do have some apps that must use root...)
Thanks,
Gil.
zaventh said:
Yes, though root has nothing to do with this. The bootloader is unlocked, which is why root was obtainable via Chainfire's custom recovery. We have no restrictions on flashing custom ROMs/kernels/recoveries/etc.
Click to expand...
Click to collapse
Are we 100% certain that the bootloader is indeed unlocked. I know that chainfire stated this (although he currently doesnt own the s5).
I just came from HTC, and it states when you boot whether the bootloader is locked or unlocked. Im assuming there is no simple way of knowing whether the bootloader is locked or unlocked like the HTC devices
Phew glad to see the bootloader is not locked. Gonna root as soon as I get my replacement S5. Can't wait for the custom ROMs
Sent from my SM-G900T using XDA Premium 4 mobile app
el7145 said:
Are we 100% certain that the bootloader is indeed unlocked. I know that chainfire stated this (although he currently doesnt own the s5).
I just came from HTC, and it states when you boot whether the bootloader is locked or unlocked. Im assuming there is no simple way of knowing whether the bootloader is locked or unlocked like the HTC devices
Click to expand...
Click to collapse
There are reliable sources saying yes it is unlocked and there are reliable sources saying no it still hasn't been confirmed until someone successfully flashes a custom rom/kernel/recovery.
The consensus around here seems to be that it is unlocked but its just people repeating the words of the original few that debated it. And of course since we all want it to be unlocked, it is easier to believe that it is.
I personally don't want to jump to conclusion so i want there to be more discussion on the matter. Therefore i requested the "boot loader un/locked" thread to be reopened in Q/A.
i want to walk down to the store and buy one right now but until its confirmed im waiting it out. $650 bet!
The user lordazoroth originally posted this method here in the T-Mobile SGSIII forum. However, I have confirmed that it works with the Note 3 (at least with the Verizon variant) with one small difference. Feel free to give us both a "THANKS" if this helped you out.
You can disable the OTA Update notification by following the steps below. Just be aware that there is a small change in STEP #3.
Solution:
Step 1. Delete the update located in /cache/fota/ (may be /data/fota) and then click the update notification prompt to install it, it will instantly fail and the notification will disappear. (My phone rebooted and tried to install the update - this is the point where my Note 3 gave the update failed notification. I just rebooted the phone and went to STEP #2.)
Step 2. Disable otacerts.zip located in /etc/security by renaming it to otacerts.zip.bak
Step 3. Disable FotaClient.apk and FWUpgrade.apk by renaming with .bak extensions located in /system/app/
Step 4. Reboot
(NOTE: The difference in STEP #3 for the Galaxy Note 3 is that the [FotaClient.apk] is named [LocalFotaClient.apk] instead of just [FotaClient.apk]. All of the other steps are the same.
Continue running JB 4.3 and enjoy your Note 3 without that nagging update notification!
But the kitkat update is awesome... so you might want to reconsider doing this
Sent from my Note 3 using Tapatalk Pro
Wouldn't just freezing the "SDM" app do the trick? And possibly "FWUpgrade", although i heard that just SDM works
lmike6453 said:
Wouldn't just freezing the "SDM" app do the trick? And possibly "FWUpgrade", although i heard that just SDM works
Click to expand...
Click to collapse
You're right. Freezing just sdm would do the trick lol
Sent from my SM-N900V using Tapatalk
Grompy said:
You're right. Freezing just sdm would do the trick lol
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Say I'm not using TiBu. Can I use root explore to change something with sdm or should I just do what was originally posted?
Sent from my SM-N900V using Tapatalk
TMFGO45 said:
Say I'm not using TiBu. Can I use root explore to change something with sdm or should I just do what was originally posted?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I personally use ROM Toolbox to do it
I got the annoying OTA update today... I DON'T WANT TO UPDATE!!! Why can't they give us an option instead of forcing it down our throats?
Is there any way to disable the update WITHOUT ROOTING? I read everywhere you need ROOT ACCESS to delete the SDM.apk FILE and such. I can't delete it without root.
How can I get rid of the annoying update WITHOUT ROOTING or what is the easiest way to gain root without wiping out everything and starting over?
As of this morning...Verizon seems to be trying to "ram the update" onto your note 3
I was rooted and safestrapped on MJE and when I unplugged my phone from the charger this morning...I had a notice that the update failed to install.
I had previously downloaded, but removed the download.
Sent from my Note 3 via Tapatalk
boamuro said:
I got the annoying OTA update today... I DON'T WANT TO UPDATE!!! Why can't they give us an option instead of forcing it down our throats?
Is there any way to disable the update WITHOUT ROOTING? I read everywhere you need ROOT ACCESS to delete the SDM.apk FILE and such. I can't delete it without root.
How can I get rid of the annoying update WITHOUT ROOTING or what is the easiest way to gain root without wiping out everything and starting over?
Click to expand...
Click to collapse
rooting (with jb roms, for us vzw n3 owners) does not wipe anything at all. Kingo is easy. There's how-to threads and vids.
Edit: This is what I recommend. ..
http://forum.xda-developers.com/showthread.php?t=2543386
Edit 2: no way to disable the ota update notification w/o root.
LeftyGR said:
rooting (with jb roms, for us vzw n3 owners) does not wipe anything at all. Kingo is easy. There's how-to threads and vids.
Edit: This is what I recommend. ..
http://forum.xda-developers.com/showthread.php?t=2543386
Edit 2: no way to disable the ota update notification w/o root.
Click to expand...
Click to collapse
OMG!! I was able too root easily, but the stupid OTA update popped up and I accidentally hit the UPDATE button. Now it rebooted on its own and went into this RECOVERY MODE and it's trying to update... I removed the battery out right away... HOW CAN I CANCEL IT?! OMG! Somone help me please. It was going so well and I can't believe the stupid popup got me...
---------- Post added at 06:23 PM ---------- Previous post was at 06:19 PM ----------
Am I doomed??? OMG I hate you Verizon
boamuro said:
OMG!! I was able too root easily, but the stupid OTA update popped up and I accidentally hit the UPDATE button. Now it rebooted on its own and went into this RECOVERY MODE and it's trying to update... I removed the battery out right away... HOW CAN I CANCEL IT?! OMG! Somone help me please. It was going so well and I can't believe the stupid popup got me...
---------- Post added at 06:23 PM ---------- Previous post was at 06:19 PM ----------
Am I doomed??? OMG I hate you Verizon
Click to expand...
Click to collapse
No way of knowing how far it got. If it was able to get the bootloader nailed in...yes. Screwed. Welcome to kk. If not, whatever you do will wipe at this point.
Safest bet to try and see if you can retain jb is with odin...if it lets you. If it does, great. If it doesn't, you still need odin because you just interrupted a firmware update and probably just soft bricked your phone. So you'll need odin to put kk on your phone.
--
If niether of these things look good, they aren't. So try this first. Try booting to recovery. If you can, it's possible you just saved yourself from learning to use odin. Do a factory reset and reboot. See if it boots to jb. If it does, root asap. If not (it just hangs forever or loops), you're bricked. Try to odin jb. If it keeps failing, you're stuck with kk and you need to odin kk.
If you can't get to recovery and just hangs or loops, odin jb or kk. Whichever it lets you.
If it doesn't let you boot to recovery because it continues to upgrade, at this point let it. This is the ONLY possible scenario that you will keep anything.
Mind you, everything I just covered will never touch any files on external sd memory.
This is a lot to process. So take your time. Good luck!
Odin tutorials are in the general section.
<Note3>
LeftyGR said:
No way of knowing how far it got. If it was able to get the bootloader nailed in...yes. Screwed. Welcome to kk. If not, whatever you do will wipe at this point.
Safest bet to try and see if you can retain jb is with odin...if it lets you. If it does, great. If it doesn't, you still need odin because you just interrupted a firmware update and probably just soft bricked your phone. So you'll need odin to put kk on your phone.
--
If niether of these things look good, they aren't. So try this first. Try booting to recovery. If you can, it's possible you just saved yourself from learning to use odin. Do a factory reset and reboot. See if it boots to jb. If it does, root asap. If not (it just hangs forever or loops), you're bricked. Try to odin jb. If it keeps failing, you're stuck with kk and you need to odin kk.
If you can't get to recovery and just hangs or loops, odin jb or kk. Whichever it lets you.
If it doesn't let you boot to recovery because it continues to upgrade, at this point let it. This is the ONLY possible scenario that you will keep anything.
Mind you, everything I just covered will never touch any files on external sd memory.
This is a lot to process. So take your time. Good luck!
Odin tutorials are in the general section.
<Note3>
Click to expand...
Click to collapse
GRRR it installed Kitkat successfully. I'm SO MAD.. I should have set the annoying OTA notification for a different time so that it wouldn't constantly pop up every second... I would have been home free rooted on Jellybean if it weren't for the STUPID UPDATE.
So can I still DOWNGRADE to Jellybean and be rooted? or did Verizon LOCK or restrict stuff with the update? Can I go back to Jellybean keeping all my files?
boamuro said:
GRRR it installed Kitkat successfully. I'm SO MAD.. I should have set the annoying OTA notification for a different time so that it wouldn't constantly pop up every second... I would have been home free rooted on Jellybean if it weren't for the STUPID UPDATE.
So can I still DOWNGRADE to Jellybean and be rooted? or did Verizon LOCK or restrict stuff with the update? Can I go back to Jellybean keeping all my files?
Click to expand...
Click to collapse
I heard once you take the verizon ota update for now your locked down.
Sent from my SM-N900V using xda premium
Hulk0069 said:
I heard once you take the verizon ota update for now your locked down.
Sent from my SM-N900V using xda premium
Click to expand...
Click to collapse
I read that too... I can't believe one simple tap mistake ruined my whole first time rooting adventure... Using KINGO was so easy and right when I WAS ABOUT TO DELETE THE STUPID SDM file in the system folder, the update popup came up and accidentally hit the UPDATE And it just rebooted instantly!! I hate how they don't even allow you to cancel or anything... like totally forcing it in your face!!
I still have SuperSU but no longer functions it says "There isn o SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
So there's no way to have root access now?? I can't flash back to Jellybean??? Verizon/Samsung really screwed us here. There must be a way to have root access in Jellybean... I don't care for custom roms... I just want root access!!
boamuro said:
I read that too... I can't believe one simple tap mistake ruined my whole first time rooting adventure... Using KINGO was so easy and right when I WAS ABOUT TO DELETE THE STUPID SDM file in the system folder, the update popup came up and accidentally hit the UPDATE And it just rebooted instantly!! I hate how they don't even allow you to cancel or anything... like totally forcing it in your face!!
I still have SuperSU but no longer functions it says "There isn o SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
So there's no way to have root access now?? I can't flash back to Jellybean??? Verizon/Samsung really screwed us here. There must be a way to have root access in Jellybean... I don't care for custom roms... I just want root access!!
Click to expand...
Click to collapse
It's verizon not Sammy who did this
Sent from my SM-N900V using xda premium
Hulk0069 said:
It's verizon not Sammy who did this
Sent from my SM-N900V using xda premium
Click to expand...
Click to collapse
AH EVIL VERIZON... freaking Verizon...
There seriously is no way to flash back to Jellybean and be rooted??? or be rooted in Kitkat?? This is SO RIDICULOUS..
I'm at least glad FoxFi fixed a way to still work with KitKat... if they didn't, I'd be really pissed to have no hotspot and stuck with KitKat... screw you VERIZON.
boamuro said:
AH EVIL VERIZON... freaking Verizon...
There seriously is no way to flash back to Jellybean and be rooted??? or be rooted in Kitkat?? This is SO RIDICULOUS..
I'm at least glad FoxFi fixed a way to still work with KitKat... if they didn't, I'd be really pissed to have no hotspot and stuck with KitKat... screw you VERIZON.
Click to expand...
Click to collapse
As it has been warned now many, many, many times.... There is NO GOING BACK if you take the NC4 update. Also, as of now, there also NO root method for it. You're stuck on it.
Sent From The Darkside of My N3
mwshows said:
As it has been warned now many, many, many times.... There is NO GOING BACK if you take the NC4 update. Also, as of now, there also NO root method for it. You're stuck on it.
Sent From The Darkside of My N3
Click to expand...
Click to collapse
So it would be pointless for me to try to use Odin to flash back to stock Jellybean and then KINGO? It won't even flash back?
I did successfully root before OTA installed Kitkat on mine... does that make any difference?
boamuro said:
So it would be pointless for me to try to use Odin to flash back to stock Jellybean and then KINGO? It won't even flash back?
I did successfully root before OTA installed Kitkat on mine... does that make any difference?
Click to expand...
Click to collapse
Unfortunately no. Once you have nc4 loaded you cannot go backwards.
<Note3>
bummer
Can anyone post a twrp backup of stock kitkat 4.4.4?
http://forum.xda-developers.com/showthread.php?t=2701376 isn't that what this has?
-Epix- said:
http://forum.xda-developers.com/showthread.php?t=2701376 isn't that what this has?
Click to expand...
Click to collapse
It is, but the collection doesn't include the 4.4.4 AT&T nandroid.
The nandroids are primarily intended for carrier variants that (for so long) did not have access to RUUs. Every AT&T update has had a corresponding RUU, so you don't see many stock nandroids posted.
RUU may just be easier than hunting down a stock nandroid. Although it depends on what the OP intends to do.
I will see if I did a backup before I thought I did but my luck doubt it.
I know why I posted that link. I didn't see any service. I appologize
Thanks for the responses, I was trying to get back to stock so that I can s-off. I tried the ruu but for some reason it won't run on my PC. Ive read around the forum and people have had this same issue but I couldn't fix it.
Sent from my unknown using XDA Premium 4 mobile app
moe3516 said:
Thanks for the responses, I was trying to get back to stock so that I can s-off. I tried the ruu but for some reason it won't run on my PC. Ive read around the forum and people have had this same issue but I couldn't fix it.
Sent from my unknown using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I wasn't stock when I s-off well I was rooted but stock rom. 5.0.2
Also with that link just search what your Cid is via fastboot commands and download the according backup file. Isn't that the same thing.?
I'm really trying to get more into helping and knowing so please don't hate me If I'm wrong just help correct me. )
Example for me I'm att cw101. So under the Nandroid TWRP backup area look for the cw101 and download file
I read that you should be as close to stock as possible and I like a fool forgot to copy my nandroid backup of my stock rom to my ext sd card when I re unlocked my bootloader. So you were rooted and on stock rom?
Sent from my unknown using XDA Premium 4 mobile app
Don't quote me. I was seriously having issues because my cid said one thing and the ruu I was trying to use said another.
I would wait for another opinion I'm a noob helper
Thanks
Sent from my unknown using XDA Premium 4 mobile app
So my question is Nandroid backup the only way to go back to stock. Can you do a ruu
You can definitely use RUU to revert to stock. My PC was having issues running the RUU so I was just trying to restore a nandroid backup of kitkat 4.4.4. I
Sent from my unknown using XDA Premium 4 mobile app
moe3516 said:
You can definitely use RUU to revert to stock. My PC was having issues running the RUU so I was just trying to restore a nandroid backup of kitkat 4.4.4. I
Sent from my unknown using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah i was having issues with Windows 7 64 bit. I had to use the wife's computer which is windows 8
-Epix- said:
Also with that link just search what your Cid is via fastboot commands and download the according backup file. Isn't that the same thing.?
Click to expand...
Click to collapse
The nandroid collection thread you linked doesn't have the version the OP is looking for (4.4.4) I already said that. It only has 4.4.2.
---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------
-Epix- said:
Yeah i was having issues with Windows 7 64 bit. I had to use the wife's computer which is windows 8
Click to expand...
Click to collapse
Win8 usually causes more issues with RUU than Win7. If your Win7 PC didn't work, it may have been due to USB 3.0 being present (known issue) or a driver issue (very common).
What PC will/will not work is pretty random. My work laptop (Win7) works with no problem. My home PC (also Win7), I needed to uninstall HTC drivers and use "generic" Android MTP drivers to get everything (fastboot, adb, access to internal storage) to work.
It's an alienware area51 7500 (before dell took over) so it's all possible but every thing else worked fine I could connect transfer use adb perfectly. Ruu was only issue
Found this user says it's stock backup. Forgot to copy it one second.
http://forum.xda-developers.com/att...nt/att-stock-backups-recoveries-otas-t2855966
-Epix- said:
Found this user says it's stock backup. Forgot to copy it one second.
http://forum.xda-developers.com/att...nt/att-stock-backups-recoveries-otas-t2855966
Click to expand...
Click to collapse
Again, its not the version the OP wants. Android 4.4.4 = software 3.xx. The thread only has 1.xx and 2.xx softwares (4.4.2 and 4.4.3).
Not trying to be contrarian, so hope it doesn't seem that way. I know you mean well.
Like i said im a nooblet.
-Epix- said:
Like i said im a nooblet.
Click to expand...
Click to collapse
Yup, understood; and there is nothing wrong with that.
Just trying to point things out, since that is how you will learn.
Its possible that the 4.4.4 nandroid (that the OP wants) is buried somewhere in an existing thread. But I can't recall seeing one posted in the top post of a stock nandroid collection(or similar type thread). The OP's best bet is probably someone to post the nandroid here (and that is what he is asking for).
I could RUU back to 4.4.4 (possible with s-off), make a nandroid and post it. But I don't have time to do that for a while due to kids and business travel. And it would be a significant effort, since then I would then have to RUU back to Lollipop, install TWRP again, and restore back to my current setup. Lots of steps.
I downloaded the 4.4.2 last night. I was on 5.0.2 s-off unlocked rooted. After process was done it asked me if I wanted to install su. I did booted up rooted. What I can do is what you spoke of. I can update to 4.4.4 and then factory reset to get my stuff off and upload. My connection isn't the fastest for upload so it would take some time.
-Epix- said:
I downloaded the 4.4.2 last night. I was on 5.0.2 s-off unlocked rooted. After process was done it asked me if I wanted to install su. I did booted up rooted. What I can do is what you spoke of. I can update to 4.4.4 and then factory reset to get my stuff off and upload. My connection isn't the fastest for upload so it would take some time.
Click to expand...
Click to collapse
After you update to 4.4.4, in TWRP, I think you can select to just backup the boot and system partitions (and don't select data). Then the nandroid shouldn't contain any personal data, and save you from a factory reset (if that helps at all).
Yeah that would help. Lol
long story short
htc desire 610, rooted, bootloader unlocked
needed to bypass safetynet
used magisk 12.4 worked fine, new update came
magisk no longer worked, forced me to update
update bricked my phone, bypassed this by reflashing rom in recovery
researched why new magisk update was being stubborn, one suggested updating my TWRP to latest build
updated TWRP, flashed the img while in recovery, ended up putting recovery into my boot (following a guide and wasnt paying attention)
phone now stuck in bootloop, can only go in recovery
wiped and formatted everything, decided to use adb sideload as its worked wonders for me before to try and put my rom back in
adb sideload wont detect phone, after many troublesome hours i decided to follow yet another guide i found about installing a RUU file into my phone to recover
followed guide step by step, turns out htc phones need bootloader locked, wasnt mentioned in guide
p̶h̶o̶n̶e̶ ̶n̶o̶w̶ ̶s̶t̶u̶c̶k̶ ̶i̶n̶ ̶R̶U̶U̶ ̶m̶o̶d̶e̶ ̶w̶i̶t̶h̶
S̶E̶C̶U̶R̶I̶T̶Y̶ ̶F̶A̶I̶L̶!̶ ̶
R̶U̶U̶ ̶ ̶
h̶a̶v̶n̶t̶ ̶b̶e̶e̶n̶ ̶a̶b̶l̶e̶ ̶t̶o̶ ̶r̶e̶s̶t̶a̶r̶t̶ ̶i̶t̶ ̶y̶e̶t̶ ̶h̶a̶v̶e̶ ̶t̶o̶ ̶w̶a̶i̶t̶ ̶u̶n̶t̶i̶l̶ ̶b̶a̶t̶t̶e̶r̶y̶ ̶d̶i̶e̶s̶ ̶(̶t̶h̶a̶n̶k̶s̶)̶ ̶d̶o̶n̶t̶ ̶h̶a̶v̶e̶ ̶s̶c̶r̶e̶w̶d̶r̶i̶v̶e̶r̶ ̶t̶o̶ ̶t̶a̶k̶e̶ ̶b̶a̶t̶t̶e̶r̶y̶ ̶o̶u̶t̶,̶ ̶o̶t̶h̶e̶r̶s̶ ̶h̶a̶v̶e̶ ̶s̶a̶i̶d̶ ̶r̶e̶s̶t̶a̶r̶t̶i̶n̶g̶ ̶w̶o̶n̶t̶ ̶f̶i̶x̶ ̶i̶t̶
please help....
ive read many pages about similar issues, some saying boot into fastboot, some saying "just type in cmd prompt" with an attached line of code... others saying "its easy just unlock your bootloader" but what i dont understand is how i can do this??
update: can get back into TWRP not sure what i can do from here as i dont have an SD card reader to transfer files just a usb and a phone with no OS
Swaaz said:
long story short
htc desire 610, rooted, bootloader unlocked
needed to bypass safetynet
used magisk 12.4 worked fine, new update came
magisk no longer worked, forced me to update
update bricked my phone, bypassed this by reflashing rom in recovery
researched why new magisk update was being stubborn, one suggested updating my TWRP to latest build
updated TWRP, flashed the img while in recovery, ended up putting recovery into my boot (following a guide and wasnt paying attention)
phone now stuck in bootloop, can only go in recovery
wiped and formatted everything, decided to use adb sideload as its worked wonders for me before to try and put my rom back in
adb sideload wont detect phone, after many troublesome hours i decided to follow yet another guide i found about installing a RUU file into my phone to recover
followed guide step by step, turns out htc phones need bootloader locked, wasnt mentioned in guide
phone now stuck in RUU mode with
SECURITY FAIL!
RUU
havnt been able to restart it yet have to wait until battery dies (thanks) dont have screwdriver to take battery out, others have said restarting wont fix it
please help....
ive read many pages about similar issues, some saying boot into fastboot, some saying "just type in cmd prompt" with an attached line of code... others saying "its easy just unlock your bootloader" but what i dont understand is how i can do any of this when my phone is stuck in RUU mode??
Click to expand...
Click to collapse
Can't help with the issue but, the waiting on battery to die issue you can press and hold power button for 8 seconds to force it to turn off
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
Can't help with the issue but, the waiting on battery to die issue you can press and hold power button for 8 seconds to force it to turn off
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
this worked, i must of given up at exactly 7 seconds lol
dumb question but with all these programs ive downloaded tonight ive just about given up
if i factory reset my phone in android recovery mode (not TWRP, the one with the 4 androids) on a phone that doesnt have an OS installed there isnt some miracle chance it would revert to stock rom would it? the only thing on my phone is TWRP and i was using CM12 before everything spiraled out of control
update - phone can access TWRP so im back to square one, i tried RUU i tried adb sideload and i also tried the folliwing programs
sdkmanager
SP flash tool (cant be used with htc)
windroid toolkit
USDDeview
ODIN
i just want to start over and try again but i cant seem to fix this
No, factory reset just reinstalls the OS that was on the device. If you brick the device it doesn't have an OS to reinstall.
Unfortunately, I can't help you very much as I wasn't able to fix my Galaxy S4 that was bricked trying to unroot as my carrier data was slow and I couldnt find the series of files including Bootloader and OS that I used on my Galaxy Discover that fixed it (obviously galaxy s4 series of files) as Odin will flash stock os and with some work around flash custom os.
Sent from my Z988 using Tapatalk
---------- Post added at 06:17 AM ---------- Previous post was at 06:16 AM ----------
The power reset is 6-15 seconds on devices but stock Android has included this feature since Android 4.0 at the earliest that I know of
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
No, factory reset just reinstalls the OS that was on the device. If you brick the device it doesn't have an OS to reinstall.
Unfortunately, I can't help you very much as I wasn't able to fix my Galaxy S4 that was bricked trying to unroot as my carrier data was slow and I couldnt find the series of files including Bootloader and OS that I used on my Galaxy Discover that fixed it (obviously galaxy s4 series of files) as Odin will flash stock os and with some work around flash custom os.
Sent from my Z988 using Tapatalk
---------- Post added at 06:17 AM ---------- Previous post was at 06:16 AM ----------
The power reset is 6-15 seconds on devices but stock Android has included this feature since Android 4.0 at the earliest that I know of
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
its all good i feel like theres hope now that i can get back into recovery, tense moments such as these means id prob never of held down that button for more than 7 seconds to begin with and id still be stuck from RUU mode atleast.
just wish i knew how to get adb sideload to work its worked in the past but i cant get it to detect and the guide im reading says i have to use SP flash tool but i cant use scatter files on an htc phone.
Swaaz said:
its all good i feel like theres hope now that i can get back into recovery, tense moments such as these means id prob never of held down that button for more than 7 seconds to begin with and id still be stuck from RUU mode atleast.
just wish i knew how to get adb sideload to work its worked in the past but i cant get it to detect and the guide im reading says i have to use SP flash tool but i cant use scatter files on an htc phone.
Click to expand...
Click to collapse
Hope you can figure it out
Sent from my Z988 using Tapatalk
---------- Post added at 06:37 AM ---------- Previous post was at 06:23 AM ----------
Swaaz said:
its all good i feel like theres hope now that i can get back into recovery, tense moments such as these means id prob never of held down that button for more than 7 seconds to begin with and id still be stuck from RUU mode atleast.
just wish i knew how to get adb sideload to work its worked in the past but i cant get it to detect and the guide im reading says i have to use SP flash tool but i cant use scatter files on an htc phone.
Click to expand...
Click to collapse
I don't really know adb very much as I haven't really had much experience with it.
Will probably be picking up a nexus 6 and rooting it since those are 100% stock Android and are easy to root and unbrick etc I will definitely be getting more experience with adb and root
Sent from my Z988 using Tapatalk
guess its too late in the night for anyone else's assistance ill be back tomorrow morning hopefully my boss doesnt get mad at my phone being bricked. not sure if bumping threads is allowed here so i apologize in advance
Yes its allowed as far as I know
Sent from my Z988 using Tapatalk
---------- Post added at 07:37 AM ---------- Previous post was at 07:37 AM ----------
Swaaz said:
guess its too late in the night for anyone else's assistance ill be back tomorrow morning hopefully my boss doesnt get mad at my phone being bricked. not sure if bumping threads is allowed here so i apologize in advance
Click to expand...
Click to collapse
Did you try to root your only phone, that's a very bad idea
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
Yes its allowed as far as I know
Sent from my Z988 using Tapatalk
---------- Post added at 07:37 AM ---------- Previous post was at 07:37 AM ----------
Did you try to root your only phone, that's a very bad idea
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
ive rooted before, and since its rooted its easier to recover in circumstances such as these
the magisk update is what started it, old magisk stopped working and it forced me to update and that caused everything to spiral out of control
Swaaz said:
ive rooted before, and since its rooted its easier to recover in circumstances such as these
the magisk update is what started it, old magisk stopped working and it forced me to update and that caused everything to spiral out of control
Click to expand...
Click to collapse
My suggestion is don't use magisk
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
My suggestion is don't use magisk
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
unfortunately nintendo apps have decided to label anyone with a bootloader unlocked as a filthy hacker and block access to their games
god forbid i upgrade my stock rom
That's why I try to have multiple devices to use
Sent from my Z988 using Tapatalk
bump
disappointed... guess ill go buy an SD card reader and try and transfer the rom that way. people might think thread was solved due to how many replies there was :X
Swaaz said:
disappointed... guess ill go buy an SD card reader and try and transfer the rom that way. people might think thread was solved due to how many replies there was :X
Click to expand...
Click to collapse
I don't think so...
Sent from my Z988 using Tapatalk
back to square one, new magisk update came out today which claims to not brick phones... still bricks mine
i guess thread closed. nobody here and every 2 hours i come into a different problem so ill just keep toying with it
if anyone cares, my current issue is that i cannot flash the current TWRP it always results in a bootloop im currently using an older build and ive been told that i need the newest TWRP for the newest magisk build