Related
I installed deodexed 4.2.2 stock when i was running deodexed 4.2.1 stock. i felt that it was buggy, so i went into cwrecovery and wiped it and i was about to begin reinstalling deodexed 4.2.2 again when i noticed i forgot to put it onto my phone. then i tried to use my phone, and it would be stuck at "unfortunately, system ui has stopped". it never leaves that popup, so i can't enable usb debugging. i can't use recovery mode, because when i do, the android with a triangle caution sign is there, but no options to select from. i can enter fastboot mode, but that's about it.
CM9onmyMoPho said:
I installed deodexed 4.2.2 stock when i was running deodexed 4.2.1 stock. i felt that it was buggy, so i went into cwrecovery and wiped it and i was about to begin reinstalling deodexed 4.2.2 again when i noticed i forgot to put it onto my phone. then i tried to use my phone, and it would be stuck at "unfortunately, system ui has stopped". it never leaves that popup, so i can't enable usb debugging. i can't use recovery mode, because when i do, the android with a triangle caution sign is there, but no options to select from. i can enter fastboot mode, but that's about it.
Click to expand...
Click to collapse
Reflash a factory image in fastboot, flash CWM/TWRP in fastboot, reroot and reflash the dedexed rom. Your phone isn`t even a bit bricked fortunately.
gee2012 said:
Reflash a factory image in fastboot, flash CWM/TWRP in fastboot, reroot and reflash the dedexed rom. Your phone isn`t even a bit bricked fortunately.
Click to expand...
Click to collapse
How can I reflash the factory image? and where can i find instructions? where can i find the link to download the factory image? thanks
CM9onmyMoPho said:
How can I reflash the factory image? and where can i find instructions? where can i find the link to download the factory image? thanks
Click to expand...
Click to collapse
Look in my signature line 2 and 3.
gee2012 said:
Look in my signature line 2 and 3.
Click to expand...
Click to collapse
thanks. will i lose any personal things such as photos?
CM9onmyMoPho said:
thanks. will i lose any personal things such as photos?
Click to expand...
Click to collapse
Everything will be lost. Considering your phone is bricked there is no way to pull the pictures from your device.
Edit: you might not have to flash full stock, just the system.img that will allow you to overwrite the current system and maintain your sdcard.
i do not know if this is the best place to post this considering i am brand new (i hope so) but i have a soft bricked nexus s 4g that i am trying to fix.
it was loaded with the helly bean 4.2.2 custom rom from nexus hacks (sorry no links) after the reboot it went to a black screen.
what ive tried:
odin: flashing a new rom, this resulted in odin not finding the device (usb debugging is not on and i cant turn it on)
fastboot: (i have all the files but i cant seem to get it set up, i type in adb or fastboot (no device recognized)
nexus root toolkit: (wouldnt find the device and found no options to help with usb debugging)
dfs: (couldnt read the device)
plugging in the phone to the computer: it makes the noise that it is plugged in, comes up as f drive but it is greyed out and i cant click on it (says insert disc)
clock work recovery: i did a full data wipe and required wipes cache and delvik or something along those lines: it reboots into the rom and nothing has changed.. my guess is because there is no back up of the original rom and the cfw is trash, it just wipes the bad rom back to factory and that is still a problem.
pda net: wont recognize the device
galaxy nexus toolkit: nothing useful since the usb debugging is not enabled.
ive worked for 6 hours as of last night to figure this out. i have spent most of those hours in forums and delving further into this phone then id imagined (its not mine) so if there is anyone out there that can suggest anything id appreciate it. this has got me stumped and amazed how such easy fix can really be this complicated.. i will thank any and all answers given to me
theblackrose666 said:
i do not know if this is the best place to post this considering i am brand new (i hope so) but i have a soft bricked nexus s 4g that i am trying to fix.
it was loaded with the helly bean 4.2.2 custom rom from nexus hacks (sorry no links) after the reboot it went to a black screen.
what ive tried:
odin: flashing a new rom, this resulted in odin not finding the device (usb debugging is not on and i cant turn it on)
fastboot: (i have all the files but i cant seem to get it set up, i type in adb or fastboot (no device recognized)
nexus root toolkit: (wouldnt find the device and found no options to help with usb debugging)
dfs: (couldnt read the device)
plugging in the phone to the computer: it makes the noise that it is plugged in, comes up as f drive but it is greyed out and i cant click on it (says insert disc)
clock work recovery: i did a full data wipe and required wipes cache and delvik or something along those lines: it reboots into the rom and nothing has changed.. my guess is because there is no back up of the original rom and the cfw is trash, it just wipes the bad rom back to factory and that is still a problem.
pda net: wont recognize the device
galaxy nexus toolkit: nothing useful since the usb debugging is not enabled.
ive worked for 6 hours as of last night to figure this out. i have spent most of those hours in forums and delving further into this phone then id imagined (its not mine) so if there is anyone out there that can suggest anything id appreciate it. this has got me stumped and amazed how such easy fix can really be this complicated.. i will thank any and all answers given to me
Click to expand...
Click to collapse
You need to be in the bootloader for fastboot to work. Reboot to bootloader and try flashing a recovery.img using this command.
fasboot flash recovery recovery.img
It blows my mind when a user gets all this great help and hasn't given any thanks to the helpers.
Sent from my iPad 4
mitchdickson said:
It blows my mind when a user gets all this great help and hasn't given any thanks to the helpers.
Sent from my iPad 4
Click to expand...
Click to collapse
Happens all the time. I'd have 1000 extra thanks if people new how to use the button or were remotely grateful.
estallings15 said:
Happens all the time. I'd have 1000 extra thanks if people new how to use the button or were remotely grateful.
Click to expand...
Click to collapse
i am sorry i was getting sdk tools set up watching an online tut. i am very greatful for your help my problem was that i had not installed java. so if anyone finds that sdk tools is not coming up. install java and it will work like it is supposed to. i will give a thank you just like i have promised. you guys on this site are the best techs hands down
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
is there a thread on here about adb shell and pushing a new rom onto a nexus s 4g? basically the commands?
theblackrose666 said:
i am sorry i was getting sdk tools set up watching an online tut. i am very greatful for your help my problem was that i had not installed java. so if anyone finds that sdk tools is not coming up. install java and it will work like it is supposed to. i will give a thank you just like i have promised. you guys on this site are the best techs hands down
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
is there a thread on here about adb shell and pushing a new rom onto a nexus s 4g? basically the commands?
Click to expand...
Click to collapse
adb push nameofrom.zip /sdcard/
Sent from my Nexus 4 using xda premium
ran sdk tools tried adb shell and nothing it wont read the device. we tried to push the .tar files to the phone using samsung galaxy nexus tool kit. it didnt work so hes going to take it to a repair but i think the device is toast on the account that usb debugging mode is no where in sight. if it does get fixed ill be sure to report how it got fixed. so anyone else who runs into the problem can get this fixed without a 20 dollar repair bill.
heat361 said:
Everything will be lost. Considering your phone is bricked there is no way to pull the pictures from your device.
Edit: you might not have to flash full stock, just the system.img that will allow you to overwrite the current system and maintain your sdcard.
Click to expand...
Click to collapse
will my computer even detect my phone? usb debugging is off and i can't see the phone's storage from my pc.
Please help!!! Ok, let me start by saying that I've successfully rooted, soft bricked, and unbricked my previous S2 & Note 2. I just got an S4 about a month ago and decided to root today. While I was setting it up a month ago I updated to mf3 and had completely forgotten.
I did the new root via terminal and was successful. Installed SU just fine. I gave root to xplorer and switched out my build.prop for the sprint sg4 to install google wallet (the one I could actually use nfc with). Installed fine, then got an error about not having sufficient permission inside gw. I rebooted and somehow su lost binary. I've tried everything I could look up. I can't uninstall su without root, and I can't open it without the binaries. I can't replace the build.prop, or edit it. I can pull via adb but can't push. Can't do it through adb shell either. Can't use odin (cuz mf3), can't use mobile odin, can't use goo either. I'm lost.
It hasn't caused any serious problems but I'd like to have my at&t build.prop back. (Fyi, I did back it up before I did it. So I have it, I just can't replace it.)
Can this be fixed? Am I f'ed? Do I have to live with it til someone gets around the bootloader? Or do I have to take it back to bestbuy to replace it? (And if I do, Will they replace it?)
Update: BestBuy will not replace it.
Go to a best buy that has the Samsung experience. They won't replace the phone but they can flash the mf3 firmware and get you back to like new again. You'll have to sweet talk them.
You can also try visiting an att store to have them flash mf3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Thanks for the posts guys. Really appreciate it! I ended up trying to do an emergency flash via Kies. After a couple of dozen times of it failing to download (too slow) my phone ended up with the yellow triangle and said the firmware upgrade failed and to connect it to Kies. Luckily that showed that I wasn't rooted so I took it to a Samsung experience kiosk and they had me up and running in 10 minutes. Needless to say I'm not rooting again til there's a recovery for MF3!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Jd1639, the girl I spoke to yesterday wouldn't reflash it for me. She could tell it wasn't stock because of the 4G signal.
I got lucky today with Kies failing! The hubs would've killed me!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
silrosriv said:
Jd1639, the girl I spoke to yesterday wouldn't reflash it for me. She could tell it wasn't stock because of the 4G signal.
I got lucky today with Kies failing! The hubs would've killed me!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I had the exact same experience with Best buy. The lady, as friendly as she was, was unhelpful in my situation. She kept saying they do not want to flash something that has been altered in any way just in case it gets bricked... it is to prevent liability on their part (which I can kind of understand). I even told her I'd be glad to sign a waiver to assume full liability if something goes wrong. She didn't go for it... Unfortunately, I'm stuck at the moment, I'm searching out ways to restore my build.prop from either adb sideload via the stock recovery or through ODIN somehow... There was a thread discussing a fix for the yellow triangle that required ODIN to flash some files (5 or so)... So, I was thinking if I can get the same type of thing setup for build.prop, I'd be in good shape... I just have 0 experience with doing this stuff, so I'm still reading/learning how it all works.
Dusty, I think if you're on MF3 nothing is going to work. You can try an emergency firmware flash through Kies. If you're at the yellow triangle and it's telling you to connect it to Kies then look at the top and see if it says that you're running Samsung official with write block enabled. If it does then take it back to the Samsung experience kiosk and tell them your PC froze during an update and that's what broke your phone.
Hope it helps. That's what worked for me.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
dustyhughes said:
I had the exact same experience with Best buy. The lady, as friendly as she was, was unhelpful in my situation. She kept saying they do not want to flash something that has been altered in any way just in case it gets bricked... it is to prevent liability on their part (which I can kind of understand). I even told her I'd be glad to sign a waiver to assume full liability if something goes wrong. She didn't go for it... Unfortunately, I'm stuck at the moment, I'm searching out ways to restore my build.prop from either adb sideload via the stock recovery or through ODIN somehow... There was a thread discussing a fix for the yellow triangle that required ODIN to flash some files (5 or so)... So, I was thinking if I can get the same type of thing setup for build.prop, I'd be in good shape... I just have 0 experience with doing this stuff, so I'm still reading/learning how it all works.
Click to expand...
Click to collapse
Wait so you lost root, too?
What exactly is your problem?
Because you can replace your build.prop with adb easily.
Exel said:
Wait so you lost root, too?
What exactly is your problem?
Because you can replace your build.prop with adb easily.
Click to expand...
Click to collapse
Sorry, I was a bit vague... I modded the build.prop to enable lockscreen rotation, which was basically adding one line to the end of the file. I realize how dumb this was, it was late and I wasn't thinking clearly :silly:....
Well, since I modded the build.prop, I cannot boot to the OS, in fact after the Samsung boot logo it doesn't even make it to the AT&T boot screen. It remains black after Samsung boot logo. The LED does turn blue after a bit, and if I have the phone plugged into the laptop the USB drivers will install, but I never make it to the OS no matter how long I leave the phone.
So I'm stuck not being able to boot to the OS. I can get to stock recovery and have the ADB sideload option, but it seems to be different that full blown ADB (from what I've gathered).
My biggest problem now is trying to take a copy of the clean build.prop and replace the one that is messed up in /system/
I can't determine exactly what I need (update script with build.prop etc) to load over sideload to get it to work.
---------- Post added at 12:07 PM ---------- Previous post was at 12:03 PM ----------
silrosriv said:
Dusty, I think if you're on MF3 nothing is going to work. You can try an emergency firmware flash through Kies. If you're at the yellow triangle and it's telling you to connect it to Kies then look at the top and see if it says that you're running Samsung official with write block enabled. If it does then take it back to the Samsung experience kiosk and tell them your PC froze during an update and that's what broke your phone.
Hope it helps. That's what worked for me.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I can get my phone to the yellow triangle, but mine actually says custom in the top left instead of official... Because of that, I couldn't convince the lady at the kiosk to flash my phone. Granted, it wasn't on the yellow triangle yesterday when i took it. I did convince her to plug it in while I had it in download mode. It recognized my phone, but I couldn't get her to proceed with flashing it.
dustyhughes said:
Sorry, I was a bit vague... I modded the build.prop to enable lockscreen rotation, which was basically adding one line to the end of the file. I realize how dumb this was, it was late and I wasn't thinking clearly :silly:....
Well, since I modded the build.prop, I cannot boot to the OS, in fact after the Samsung boot logo it doesn't even make it to the AT&T boot screen. It remains black after Samsung boot logo. The LED does turn blue after a bit, and if I have the phone plugged into the laptop the USB drivers will install, but I never make it to the OS no matter how long I leave the phone.
So I'm stuck not being able to boot to the OS. I can get to stock recovery and have the ADB sideload option, but it seems to be different that full blown ADB (from what I've gathered).
My biggest problem now is trying to take a copy of the clean build.prop and replace the one that is messed up in /system/
I can't determine exactly what I need (update script with build.prop etc) to load over sideload to get it to work.
---------- Post added at 12:07 PM ---------- Previous post was at 12:03 PM ----------
I can get my phone to the yellow triangle, but mine actually says custom in the top left instead of official... Because of that, I couldn't convince the lady at the kiosk to flash my phone. Granted, it wasn't on the yellow triangle yesterday when i took it. I did convince her to plug it in while I had it in download mode. It recognized my phone, but I couldn't get her to proceed with flashing it.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=1236732
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
dustyhughes said:
Sorry, I was a bit vague... I modded the build.prop to enable lockscreen rotation, which was basically adding one line to the end of the file. I realize how dumb this was, it was late and I wasn't thinking clearly :silly:....
Well, since I modded the build.prop, I cannot boot to the OS, in fact after the Samsung boot logo it doesn't even make it to the AT&T boot screen. It remains black after Samsung boot logo. The LED does turn blue after a bit, and if I have the phone plugged into the laptop the USB drivers will install, but I never make it to the OS no matter how long I leave the phone.
So I'm stuck not being able to boot to the OS. I can get to stock recovery and have the ADB sideload option, but it seems to be different that full blown ADB (from what I've gathered).
My biggest problem now is trying to take a copy of the clean build.prop and replace the one that is messed up in /system/
I can't determine exactly what I need (update script with build.prop etc) to load over sideload to get it to work.
---------- Post added at 12:07 PM ---------- Previous post was at 12:03 PM ----------
I can get my phone to the yellow triangle, but mine actually says custom in the top left instead of official... Because of that, I couldn't convince the lady at the kiosk to flash my phone. Granted, it wasn't on the yellow triangle yesterday when i took it. I did convince her to plug it in while I had it in download mode. It recognized my phone, but I couldn't get her to proceed with flashing it.
Click to expand...
Click to collapse
Then I would try Kies. Leave your phone unplugged, then go to tools, upgrade and initialization, in all caps enter your device (mine is SGH-I337), click ok, enter your serial number, click ok, then plug in your phone in Odin mode. If that doesn't work you may have to wait for someone to figure out MF3 with Odin.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
silrosriv said:
Try this
http://forum.xda-developers.com/showthread.php?t=1236732
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Thanks much, I really appreciate the help. I have tried to push/pull files from my device without luck. The only option i have for ADB on my phone at the moment is the stock recovery "install over adb". It looks like the only commands I can run are "adb devices" (which lists my phone as "sideload") and "adb sideload"... I've used the sideload command to try and flash an OTA mf3 cfg file I found in another thread. the file was successfully pushed to the phone, and the update began but failed with an erro code of 7 (which is supposed to mean wrong device or something).
I was thinking if I could encapsulate the build.prop with a script into one of these update files to be pushed over sideload, I may be able to get my build.prop replaced and my phone running again. But i'm not sure how to build that file, or whether or not it would even have access to replace a file in the "/system" folder.
I'm still searching, and will update when/if I find an answer.
dustyhughes said:
Thanks much, I really appreciate the help. I have tried to push/pull files from my device without luck. The only option i have for ADB on my phone at the moment is the stock recovery "install over adb". It looks like the only commands I can run are "adb devices" (which lists my phone as "sideload") and "adb sideload"... I've used the sideload command to try and flash an OTA mf3 cfg file I found in another thread. the file was successfully pushed to the phone, and the update began but failed with an erro code of 7 (which is supposed to mean wrong device or something).
I was thinking if I could encapsulate the build.prop with a script into one of these update files to be pushed over sideload, I may be able to get my build.prop replaced and my phone running again. But i'm not sure how to build that file, or whether or not it would even have access to replace a file in the "/system" folder.
I'm still searching, and will update when/if I find an answer.
Click to expand...
Click to collapse
Not sure, correct me if I'm wrong, but I think you're in recovery (blue DOS looking menu list). Power button & volume up? That is how you get to sideload. To do regular adb you need to run an app for terminal emulator while the phone is actually on.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
silrosriv said:
Then I would try Kies. Leave your phone unplugged, then go to tools, upgrade and initialization, in all caps enter your device (mine is SGH-I337), click ok, enter your serial number, click ok, then plug in your phone in Odin mode. If that doesn't work you may have to wait for someone to figure out MF3 with Odin.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm afraid you are right... If MF3 were available through Kies (since I was unfortunate enough to get a phone with mf3) i'd be ok... but i think i may just be waiting a while.... My wife has the same phone, so if i could image hers, I could go that route... but again, out of my area of expertise.
---------- Post added at 12:29 PM ---------- Previous post was at 12:28 PM ----------
silrosriv said:
Not sure, correct me if I'm wrong, but I think you're in recovery (blue DOS looking menu list). Power button & volume up? That is how you get to sideload. To do regular adb you need to run an app for terminal emulator while the phone is actually on.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
you are correct, I cannot get to the phone's os for full blown adb...
dustyhughes said:
I'm afraid you are right... If MF3 were available through Kies (since I was unfortunate enough to get a phone with mf3) i'd be ok... but i think i may just be waiting a while.... My wife has the same phone, so if i could image hers, I could go that route... but again, out of my area of expertise.
---------- Post added at 12:29 PM ---------- Previous post was at 12:28 PM ----------
you are correct, I cannot get to the phone's os for full blown adb...
Click to expand...
Click to collapse
I kind of want to try for you..
You have TeamViewer? It's a remote access app for your PC so I can run some commands on your PC (adb)
dustyhughes said:
I'm afraid you are right... If MF3 were available through Kies (since I was unfortunate enough to get a phone with mf3) i'd be ok... but i think i may just be waiting a while.... My wife has the same phone, so if i could image hers, I could go that route... but again, out of my area of expertise.
---------- Post added at 12:29 PM ---------- Previous post was at 12:28 PM ----------
you are correct, I cannot get to the phone's os for full blown adb...
Click to expand...
Click to collapse
Have you tried to boot in safe mode? I don't think it will let you change anything though.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Exel said:
I kind of want to try for you..
You have TeamViewer? It's a remote access app for your PC so I can run some commands on your PC (adb)
Click to expand...
Click to collapse
I do not have teamviewer currently installed. I've been using LogMeIn since it was completely free and kind of just stuck with it. I've also used join.me for the one off remote assistance situations.
i would be willing to allow you to try. I currently have ADB installed and have updated the windows path environment to use ADB universally, so there's no need to be in any certain directory.
I would be willing to allow you to attempt something... I'm almost desperate at this point
Sorry for the delay, I'm still at work, and something came up.
You guys can also try Join.me totally free.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
silrosriv said:
Have you tried to boot in safe mode? I don't think it will let you change anything though.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
i'm not sure what you mean about safe mode, is there a hardware key combination required for it?
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
silrosriv said:
You guys can also try Join.me totally free.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yes, I love Join.me... I liked it more before it started "suggesting" you to buy it all the time though
dustyhughes said:
i'm not sure what you mean about safe mode, is there a hardware key combination required for it?
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Yes, I love Join.me... I liked it more before it started "suggesting" you to buy it all the time though
Click to expand...
Click to collapse
Feel free to PM me the info and whatnot and I'll see what I can do for you.
NEW 22.21.11 OTA Zip posted on the site 12/1/14
YOU MUST BE ON 22.11.6 TO UPDATE
NEW 22.11.6 OTA Zip posted on the site 11/11/14
http://www.graffixnyc.com/motox.php
OTA is there!
Instructions:
This is ONLY for the XT1095 Pure edition.. Support priority will be given to those with a XT1095. If you have another model number you will have to figure out how/if you can run this OTA. It's not up to this thread to support devices the OTA was not meant for.
IF YOU ARE ON THE FIRST SOAK TEST OTA .5 YOU CANNOT UPDATE TO .6. IT WILL FAIL! YOU WILL HAVE TO DOWNGRADE TO 4.4.4 THEN APPLY THE .6 OTA
Follow @SolarTrans Guide found here: http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
Be unaltered unrooted system. The device cannot be rooted and then unrooted.. it must be a never rooted system or the update will fail. It seems it's failing on devices that were rooted and then unrooted. On devices that were never rooted or where the user had stock back up they made prior to rooting the ota will update fine
Boot into Stock Recovery
ADB Sideload the zip
For people getting the modem error. Make sure you back up your current modem using the DD command (google if you don't know how)
After that download the AT&T modem from my website, flash it, then take the OTA. You MAY lose LTE after the update. If you do just reflash your old modem and you'll be good to go. It's also been confirmed if you reflash the AT&T modem after the update you will get LTE back.
Download Links can be found on my website: http://www.graffixnyc.com/motox.php
Also, please do not PM me for support. PM's will not be answered. Post it in the thread. It helps other's having the same issue find a solution. If it's over PM it only benefits you and not everyone else
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....
This is going to sound really nooby but do i just flash this in recovery? Or in the bootloader?
Sorry, this is my first Moto device, have had Nexus and HTC phones before this
Use ADB sideload to flash on a stock unrooted system. Went through perfectly for me and currently optimizing apps. Thanks
jellydroid13 said:
Use ADB sideload to flash on a stock unrooted system. Went through perfectly for me and currently optimizing apps. Thanks
Click to expand...
Click to collapse
So, unroot, flash stock recovery, then go to the bootloader and adb sideload?
THEindian said:
So, unroot, flash stock recovery, then go to the bootloader and adb sideload?
Click to expand...
Click to collapse
yeah but go to recovery and sideload
I'm rooted, but still stock recovery. Can I still boot to stock recovery and sideload?
Also, how do I adb sideload? Can someone explain? I have somewhat of an idea, but want to make sure before I go ahead and do so.
dmbfan13 said:
I'm rooted, but still stock recovery. Can I still boot to stock recovery and sideload?
Also, how do I adb sideload? Can someone explain? I have somewhat of an idea, but want to make sure before I go ahead and do so.
Click to expand...
Click to collapse
Yeah, so i just got it to start flashing. Yes, you have to be unrooted but this is pretty simple, to unroot:
Go to the SuperSU app, go into the 3rd tab with all the settings, in there, there should be an option, something along the lines of "clean unroot", hit that, it should only take a minute or so
If you still see the SuperSU app once thats done, go into the play store and uninstall it
You are unrooted
To flash, plug in your phone and type in "adb reboot recovery"
You'll the that little android, once you see this, press the UP volume button, then power button, then release
Scroll down to where it says apply update from adb
type in "adb sideload BLAH BLAH BLAH.zip"
It should start applying. Hope this helps!
CRAP. I got an error in the installation and now it won't boot. It was something along the lines of how it didn't have the intall-recovery.sh file. Someone please help!
Can be root achieved?
sent from my Nexus 7
THEindian said:
Yeah, so i just got it to start flashing. Yes, you have to be unrooted but this is pretty simple, to unroot:
<snip snip>
CRAP. I got an error in the installation and now it won't boot. It was something along the lines of how it didn't have the intall-recovery.sh file. Someone please help!
Click to expand...
Click to collapse
Same thing happened to me. I suppose we'll have to flash stock back?
THEindian said:
Yeah, so i just got it to start flashing. Yes, you have to be unrooted but this is pretty simple, to unroot:
Go to the SuperSU app, go into the 3rd tab with all the settings, in there, there should be an option, something along the lines of "clean unroot", hit that, it should only take a minute or so
If you still see the SuperSU app once thats done, go into the play store and uninstall it
You are unrooted
To flash, plug in your phone and type in "adb reboot recovery"
You'll the that little android, once you see this, press the UP volume button, then power button, then release
Scroll down to where it says apply update from adb
type in "adb sideload BLAH BLAH BLAH.zip"
It should start applying. Hope this helps!
CRAP. I got an error in the installation and now it won't boot. It was something along the lines of how it didn't have the intall-recovery.sh file. Someone please help!
Click to expand...
Click to collapse
It seems like either the install-recovery.sh file was removed when you unrooted (SuperSU uses that file) or it detects it has been modified and is failing. You will have to ask someone to pull it from a non rooted device
I assume so, trying to do this but i have yet to find a stock image, the only is the one OP has his website is almost down. Do you know where else i could get an image?
---------- Post added at 05:18 AM ---------- Previous post was at 05:14 AM ----------
Could you mirror your system.img to dropbox or mega or something? The download for the system.img is taking 1 day.
Is there a guide to re-root?
will I get the next OTA if I sideload the soak test?
just wondering.
Mine is also bricked due to using unroot in supersu....
THEindian said:
I assume so, trying to do this but i have yet to find a stock image, the only is the one OP has his website is almost down. Do you know where else i could get an image?
---------- Post added at 05:18 AM ---------- Previous post was at 05:14 AM ----------
Could you mirror your system.img to dropbox or mega or something? The download for the system.img is taking 1 day.
Click to expand...
Click to collapse
I am in the same boat as you.
edwardgtxy said:
Mine is also bricked due to using unroot in supersu....
Click to expand...
Click to collapse
Yeah... mine's in a bootloop that I can't seem to stop. Holding the power button doesn't actually seem to turn it off. The screen goes black... and then eventually it just starts up again.
Im getting an error that says /modem/image/modem.b00 has unexpected contents.
any clues?
matt99017d said:
Im getting an error that says /modem/image/modem.b00 has unexpected contents.
any clues?
Click to expand...
Click to collapse
Same here.
THEindian said:
I assume so, trying to do this but i have yet to find a stock image, the only is the one OP has his website is almost down. Do you know where else i could get an image?
---------- Post added at 05:18 AM ---------- Previous post was at 05:14 AM ----------
Could you mirror your system.img to dropbox or mega or something? The download for the system.img is taking 1 day.
Click to expand...
Click to collapse
No, do not mirror my files. I like to keep count of my downloads. Get a better internet connection. I downloaded the file in less than 5 minutes as others did.
It appears you need a non-rooted system image that's never been rooted. You need to be fully stock. Not rooted and then un rooted. I believe the unrooting process still leaves files in an altered state than their original. If there is a single extra character in a file, if it's the slightest smallest difference the file is considered altered and will fail OTA checks.
Quite a few people have tried this and it has worked. It seems the ones it's failing on are ones that were rooted then unrooted. Derek Ross just told me it worked like a charm for him.
any tips to stop the boot loop? I am parking mine in recovery now to drain the battery.
Btw, it seems the OTA modified modem, system and boot. So theoretically, we can just use fastboot to go back to the your imgs, and the phone should still work right?
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Krooked22 said:
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Click to expand...
Click to collapse
Assuming that the ROM is still there, you can dirty flash the ROM zip over it, and see if it works. There's no harm in trying that.
But "No OS Installed" simply means that your /system or /boot parition are not detected (means, they are empty). Now of course, the last resort is to flash the ROM all over again.
Krooked22 said:
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Click to expand...
Click to collapse
You need to provide more information. Are you on the stock ROM or a custom ROM? Stock recovery or TWRP? Had you made any changes to the device recently?
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Download the dp3 , boot into bootloader, connect to PC run installer script after you unzip the factory image " flash all" sit back and wait for phone to reboot.
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
It's that simple.
Hey thanks a lot. Couple things, and I apologize in advance for not knowing this already.
1) what's dp3
2) how do I run installer script?
I know I shift right click and open a cmd window within fastest - where I'll unzip the file - and I know how to get the phone into Bootloader.
Again, sorry for asking for simple explanations.
StormCell said:
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Click to expand...
Click to collapse
Download any ROM ( like pure Nexus) and gapps
You can use USB otg to flash the ROM using twrp or transfer the ROM file from your PC to your phone in twrp (it supports mtp)
Simply flash ROM and gapps and viola
Sent from my Nexus 6P using XDA Labs
Ok, I'm gonna tackle this tomorrow. Any recommendations on a good ROM and Kernel (Verizon). I made nice donations long ago to Franco and ROM Manager.
Thank again, everyone!
StormCell said:
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Click to expand...
Click to collapse
Download the required ROM and gapps, connect your phone to pc , type in google, Mini adb and fastboot, a page on XDA itself will come, download it, its small and install.
Then copy the ROM and gapps package to the location of the installation of the application.
Now open your recovery and tap on adb sideload, and swipe(twrp)
Go to your PC, open adb application a cmd will appear, type adb devices, it will start a daemon then will give you your device number, a number should appear. Then type
Adb sideload """"name of your ROM package""".zip
It will start installing, wait for few minutes.
Do the same for gapps
Adb sideload " name of gapps package ".zip
Then reboot
Its fixed
NOT Sent from my GT-N7100 using the XDA-developers mobile app
i42o said:
Download the dp3 , boot into bootloader, connect to PC run installer script after you unzip the factory image " flash all" sit back and wait for phone to reboot.
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
It's that simple.
Click to expand...
Click to collapse
Why are you telling him to install the Developer Preview? He wouldn't want that unless he's actually asking for it, which he isn't.
StormCell said:
Ok, I'm gonna tackle this tomorrow. Any recommendations on a good ROM and Kernel (Verizon). I made nice donations long ago to Franco and ROM Manager.
Thank again, everyone!
Click to expand...
Click to collapse
Please continue the discussion in the other thread that you posted this question in, as I said, let's not create duplicate discussions.
StormCell said:
Hey thanks a lot. Couple things, and I apologize in advance for not knowing this already.
1) what's dp3
2) how do I run installer script?
I know I shift right click and open a cmd window within fastest - where I'll unzip the file - and I know how to get the phone into Bootloader.
Again, sorry for asking for simple explanations.
Click to expand...
Click to collapse
Developer preview 3 is a Android N preview and it is very fluid, battery life is good on stock and reason I recommend this because it is simple to do, gives you good options within the ROM and is good overall but that's just my opinion.
---------- Post added at 12:35 PM ---------- Previous post was at 12:32 PM ----------
Heisenberg said:
Why are you telling him to install the Developer Preview? He wouldn't want that unless he's actually asking for it, which he isn't.
Click to expand...
Click to collapse
Dude, I'm trying to help. Beats what you said, you going detective mode on him while I'm just giving him an easy solution. Read a book or something
i42o said:
Dude, I'm trying to help. Beats what you said, you going detective mode on him while I'm just giving him an easy solution. Read a book or something
Click to expand...
Click to collapse
Lol. Maybe you missed the title under my name.
The dev preview isn't what he asked for, it isn't an easy solution, it isn't easy to come back from if he doesn't like it, it isn't even remotely what he needs. What he's looking for is a simple way to get his phone booted up and working again (a very simple request), and what you're suggesting is he install a beta OS (a complicated "solution").
If you really have a problem with a moderator requesting that a member posts in one place at a time (as per our rules), then I'm gobsmacked. If you'd care to look at the advice I gave him in the guide thread where he also posted you'd notice that I gave two solutions that:
A) Actually address the simplicity of his problem.
B) Give two simple, easy to execute, solutions that are the most common solutions you'll ever see anyone give a member in his situation. Solutions that don't involve having to install a developer preview that he never asked for.
I get that you're trying to help him, but the "solution" you provided him isn't right for his situation at all. There was no need to become defensive and aggressive when this was pointed out.
Vishal Vignesh said:
Download the required ROM and gapps, connect your phone to pc , type in google, Mini adb and fastboot, a page on XDA itself will come, download it, its small and install.
Then copy the ROM and gapps package to the location of the installation of the application.
Now open your recovery and tap on adb sideload, and swipe(twrp)
Go to your PC, open adb application a cmd will appear, type adb devices, it will start a daemon then will give you your device number, a number should appear. Then type
Adb sideload """"name of your ROM package""".zip
It will start installing, wait for few minutes.
Do the same for gapps
Adb sideload " name of gapps package ".zip
Then reboot
Its fixed
NOT Sent from my GT-N7100 using the XDA-developers mobile app
Click to expand...
Click to collapse
I'm copying files over to my Nexus now using MTP from TWRP. Can't I just copy evrything over and flash that way? Man, this seems so much more complicated than back in the day. Thanks.
Crap, wrong thread! Sorry! Got confused.
StormCell said:
I'm copying files over to my Nexus now using MTP from TWRP. Can't I just copy evrything over and flash that way? Man, this seems so much more complicated than back in the day. Thanks.
Crap, wrong thread! Sorry! Got confused.
Click to expand...
Click to collapse
Sure, this method is for those who do not wanna copy the zip package to the PC/don't have it
Sent from my GT-N7100 using XDA-Developers mobile app
Credit goes to dbgr for finding this:
https://forum.xda-developers.com/idol-4s/how-to/6055u-root-method-t3598947
Link to download .rar:
https://mega.nz/#!U24zwYbQ!MwbIX_D01OyHHldd8c_9iCmht6wzcw1duNpGO-PRyWI
This is just a simpler, more detailed guide on how to root this phone.
Forgive me for the lack of pictures, its pretty straightforward anyways. I have included a .rar with this post that has all the essential files you will need.
(I only compressed the .rar, everything else credit goes to the creators)
1. Download the rootpackage.rar i have included, and decompress to somewhere safe.
2. Install SugarQct and install the drivers that came with it. (In the SugarQct installer, not the usb driver folder)
3. After that has finished, open the usb driver folder and run the setup.vbs script there. It should only take a second or two to run.
4. Plug phone into pc.
5. Place supersu.zip onto phone. You can put this anywhere, doesn't really matter.
6. Turn phone off and place into download mode. (Phone must be plugged in to allow download mode)
4. Open sugar with phone plugged in. Be sure to upgrade sugar if you can't see the 6055u in the list.
Set to 6055u, go to options, select save user data. Now press upgrade.
5. While sugar is downloading overwrite the r*****.mbn in bin/6055-*****. This folder appears once you start to download to the phone. You must rename the twrp_recovery_idol4_6055.img to the name of the r*****.mbn.
6. Overwrite again while files are being written. Do this as many times as you please. I only overwrote it more than once as a safety precaution.
7. Before sugar has completed fully, but after files are written, this should be around the time when it starts to download more files. As long as the writing completes you are good to go.
8. Turn phone on and enter recovery mode (power + volume up).
9. In the custom recover menu tap install and install the supersu.zip from the directory you placed it in.
10. Give it a couple of seconds (mine took 30 or so)
11. Allow phone to be rebooted and its now rooted!
Now I've had some interest in using magisk instead of supersu, but i haven't been able to install it after supersu. Choose your rom to flash wisely, as its a pain in the ass to go back from.
Please enjoy your newly rooted Alcatel Idol 4!
Thanks all!
P.S. If someone can dump their standard rom before they flash supersu.zip onto their phone, i'd like to try and find a way to get a custom rom goin and that would help.
I'm not seeing the download for the .RAR file. Am I missing something?
SeanMcCarte said:
I'm not seeing the download for the .RAR file. Am I missing something?
Click to expand...
Click to collapse
I thought i attached it to the thread, give me a second and i'll try again.
Edit:
It seems my rar is too large, i'm headed to work now, but i'll try and get something uploaded in a bit.
Thank you. Much appreciated. Also,can I unplug the phone before rebooting to recovery,or does it have to be plugged in!
SeanMcCarte said:
Thank you. Much appreciated. Also,can I unplug the phone before rebooting to recovery,or does it have to be plugged in!
Click to expand...
Click to collapse
As far as i know it doesn't have to be, but when i was successful i believe i had the phone plugged in. I did try to do somethings earlier today and unplugged the phone, and it was not successful. I do not know if it was because i unplugged the phone or if it was because i had failed to rewrite the recovery flash.
Thank you. I actually didn't want to wait for .rar so I just pieced the files from the forum here. Thank you anyway,at least somebody else will get the RAR. Also,my phone was plugged in when it worked.
I got magisk working for me I unistalled super super went into twrp and installed magisk ( I needed magisk to play fire emblem heroes lol) I'm not sure if I did something else but that's what I remember doing
Is this guide working for all the idol 4 variants or just for the cricket one? I've got the 6055k and I'm wondering if this guide works for my phone too.
scofield119 said:
Is this guide working for all the idol 4 variants or just for the cricket one? I've got the 6055k and I'm wondering if this guide works for my phone too.
Click to expand...
Click to collapse
Theres another guide for the 6055k, i'm not sure if this will work for that one. I know it works for the cricket version and i see no reason why it wouldn't work for the 6055k, but it is a better idea to follow the guide made for the 6055k.
link22534 said:
I got magisk working for me I unistalled super super went into twrp and installed magisk ( I needed magisk to play fire emblem heroes lol) I'm not sure if I did something else but that's what I remember doing
Click to expand...
Click to collapse
Would you mind checking if snapchat works on magisk? I know it doesn't work on supersu, and i've unrooted my phone because i was having troubles getting it installed after supersu.
NeonWhitey said:
Would you mind checking if snapchat works on magisk? I know it doesn't work on supersu, and i've unrooted my phone because i was having troubles getting it installed after supersu.
Click to expand...
Click to collapse
Yep it works I had to change a setting to get magisk hied working it was magisk core only mode and I pass the netsaftey check
link22534 said:
Yep it works I had to change a setting to get magisk hied working it was magisk core only mode and I pass the netsaftey check
Click to expand...
Click to collapse
Thanks for the info, but funnily enough i'm having difficulties getting the damn thing rooted again.
Thanks for the write up, I've flashed and reflashed many times... you have to be carefully about when you interrupt the process. Also know that a newer version is out. Cheers mate.
I'm not sure if it's the latest version of Sugar, but I've been trying so many times, but to no avail. Has anyone had any luck on the new version?
SUGAR QCT_SP V11.3.0
I've gotten to the point that when I start the upgrade with Sugar, it says my phone is already rooted. However, when I try to access Recovery, there is no option to install TWRP. It looks like it just loaded the same old recovery...no matter how fast and how many times I replace the Rxxxxxx.mbn file.
Cheers,
Wickster
6055p
is there any guide to root 6055p model
no luck getting this to work guys, could really use some help
Having the same problems as PizzaG - tried all the timing tips no TWRP
Having the same situation as PizzaG - same Cricket version, using the newer version of Sugar QCT 11.1.3. I've tried starting right after it reaches the last written file (4095M), Ive even tried waiting until you get the vibrate and Alcatel logo (which happens at the very end of the download, but was someone's tip), same story, boots into Android recovery. Any other tips?
Possible Solution to Rooting Troubles
I was having the same troubles as the above posters. What seemed to be the problem was that I had set a pin code to unlock my device, which made it encrypted. Unfortunately, the only way to remove a pin is to do a factory reset. Anyway, I did a factory reset and ran sugar immediately after - making sure to start the phone before sugar finished - and it worked! Perhaps there is something simpler to do and I didn't have to do a factory reset, but I don't know what that is, and this worked.
Someone have try with the 6055A?
hmm, im noticing mine says encrypted as well but i never set anything for security. just the swipe. @ ThisEndsInTears did you do a factory reset from stock recovery or from withing the phone settings? Thanks much, hopefully one step closer to getting this rooted. Y has nobody developed cm for 6.0.1 for this? cm13 im pretty sure it is