Related
hi guys,
been doing a lot of reading & kind of exhausted and the head is hurting
hope someone can help me...
i had a HTC hero on orange UK brought down to India.
Trying to unlock & load a random ROM but having the bizzarest of issues.
the hero is running on stock 1.5 build 2.73.61.66
i downgraded to 2.73.61.5 assuming that would be a better way to go...
anyways the process went well... BUT..
it starts up and goes into the "first setup" page where it asks for language & then asks me to insert the sim card to make calls...
I have NO ORANGE SIM Card.
There is no way i can enter into the phone now. i could do it earlier, the phone would boot without the sim & i used it to play music & stuff.
Now decided to use the phone for wat it is meant for, but stuck in that stage.
Can anyone help me out please.
or direct me in the right direction....
is there a way to get past this and actually come to the home screen so i can continue with everything such as unlocking the phone & loading a different rom?
Await & appreciate any response
If you just want "your phone" back I think you should be able to find the official way of restoring it to default (even upgrade to HTC's android 2.1) here:
http://www.htc.com/europe/supportdownloadlist.aspx?p_id=283&act=sd&cat=all
if you get the green android robot and starts to ask you for google login etc you can click the four screen corners to go directly to Home. Like this:
23
14
afaik Android wasn't built for use without a sim - I've wondered why too. It's complicated using it with no sim. Here's what I found on google:
http://e.ntangled.net/content/howto-set-android-dev-phone-without-sim-card
Perhaps it's because it isn't activated (with your google login) and it was earlier with a sim card but now you can't because you have no working sim card
MP3 files
If you've installed a boot loader like Amon's RA Tool v1.7 (that starts instead of Android when you hold Home and Power/hang up-button 10 seconds at boot) it might give you access to the SD-memory card and your MP3s.
I think The official HTC ROMs can only be installed (the official way) using USB and a flash-programming tool from HTC on your PC.
The Android SDK software - if I remember correctly - allows you to program the phone's recovering boot ROM (a small boot ROM - not the big phone/android OS) and once you've installed a new recovery boot ROM like Amon RA tool you can install any Android ROM directly from the SD card (ROMs in a zip file) without ever needing the PC again. You can even backup the entire phone ROM to the SD card using Amon RA tool's Nandroid backup feature and restore the ROM again if a new custom ROM is bad.
> So you are telling me that I can install Amon Ra directly
> from the PC, without having any interaction with the Phone?
Yes, I think that's probably the ONLY way actually (for the recovery boot tool).
> do you think i would be able to install a new rom and
> probably get past this screen (and probably jailbreak the phone as well)??
Hmm I'm pretty sure that most custom ROMs (I can recommend a few for htc Hero GMS) let's you go directly past the startup procedure.
> btw Thanks so much for your patience dvfk
No problem.
Here's a test how to install the Amon tool using the USB command line/shell to the phone:
http://forum.xda-developers.com/showthread.php?t=561124
If you have htc Hero GSM the newest Amon RA tool is available there. Do you know about the ADB shell that comes with the SDK to control the phone over USB?
btdag:
You can't install AmonRA without root permissions, you can't get root unless you get into android. My advise - downgrade to a different rom: ftp://xda:[email protected]_2.73.405.5_WWE_release_signed_NoDriver.exe
If that boots then you should be able to gain root using my guide:
http://forum.xda-developers.com/showthread.php?t=645253
If not why not install an orange rru exe from HTC support? That might work.
Click to expand...
Click to collapse
Currently one of the most popular ROMs is CyanogenMOD and the newest version (with android 2.2) is here - they're not 100% stable though (and camera can only shoot video in build 08312010 - I now see build 09012010 is just out but I haven't tried it):
http://mirror.kanged.net/cm/nightly/hero
When it's stable it will be moved to .../cm/stable and /hero I guess.
It lacks Gmail and other closed source google apps. They can be found here and should also be installed using Amon RA recovery boot tool after the full CM6 ROM is installed:
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps_for_HDPI_devices_2
(Hero works nicely with the HDPI version of Google apps for high-res displays)
I've found another ROM, though, called FroydVillain v1.4.4 to be more stable and cam working. It's a modified copy of the CM6 and includes the google apps from the start. However to get the newest version you currently need five zip files and install them all in the number order (FroydVillain 1.4.0 - 1.4.1 and 1.4.1 - 1.4.2 etc on to 1.4.4).
Links can be found here:
http://forum.xda-developers.com/showthread.php?t=762206
letmedanz said:
well, not so good
1) trying btdags advise -
> "You can't install AmonRA without root permissions, you
> can't get root unless you get into android. My advise -
> downgrade to a different rom:
> ftp://xda:[email protected]_NoDriver.exe"
i end up with error 131. i guess this means i need a gold card. just started reading about it
Click to expand...
Click to collapse
I think this is the newest guide to root/hack your Hero:
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click
...but the link to Amon RA boot tool is outdated - there's a version 1.7 afaik (see in my earlier post).
If I remember correctly I used this old/obsolete version:
http://theunlockr.com/2009/08/08/how-to-gain-root-access-on-your-htc-hero/
letmedanz said:
2) your suggestion:
> "I've found another ROM, though, called FroydVillain
> v1.4.4 to be more stable and cam working"
> as you should know by now, am completely new to
> this, so i tried the guide:
> http://www.villainrom.co.uk/forum/showthread.php?2054
i've just reached this step:
reboot into recovery (press Home and then power on the Hero, keep Home pressed) after copying 1.4.0 & 1.4.1, But when i hold home & power, it reboots & shows an exclamation mark within a triangle, next to a phone. supposing this is not right.
Click to expand...
Click to collapse
That's because as I said first VERY first think you need to do is install the Amon RA recovery tool - and make sure home + power boots into the RA tool.
letmedanz said:
i have no ideas on adb, trying to see if thats the way and i need to learn to use it..
Click to expand...
Click to collapse
When you install the Android SDK you get the ADB command line/shell and drivers for the phone. When the phone is plugged in (and usb phone drivers intalled) you can access the phone using ADB and do anything with it.
The old/obsolete verison of unlocking/rooting your Hero describes how you use ADB:
http://theunlockr.com/2009/08/08/how-to-gain-root-access-on-your-htc-hero
...but it seems the new version of unlocking (one-click rooting) doesn't even need it.
dvfk said:
I think this is the newest guide to root/hack your Hero:
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click
Click to expand...
Click to collapse
well, that is where the problem started
Orange UK Users - Please downgrade your ROM version to 2.73.61.5 using this HTC Program. Then you can follow the rest of this procedure as it is written. Good luck!
i had the .66 version, after reading the above, i downgraded to the .5 version.
After the install, it boots, reaches the initial setup page.
First asks for language, next screen is "Insert sim to make calls"
so unable to proceed....
...and in this guide you get stock too?
http://theunlockr.com/2009/08/08/how-to-gain-root-access-on-your-htc-hero
It mentions USB debugging must be on (so you need to access Settings I guess) but it's worth a try.
At work now.. so will need to try after heading home
Any progress?
well... just tried the obsolete htc hero root method
**How To: Gain Root Access on Your HTC Hero (OBSOLETE)**
Steps 1 to 10 are smooth, no issues
Step 11 . If the serial number and the word fastboot next to it popped up, then go back to the command prompt on the computer and type
fastboot boot cm-hero-recovery.img
here i get an error-
downloading 'boot.img'... FAILED <remote: not allow>
so stumped there..
checked in unlockr.com & they says to get past this stage i need to create a gold card...
which obviously is not possible i cant get into android...
Any suggetions/comments/help ???
Why not to flash a custom ROM?
Sent from my GT-S5660 using xda premium
Hello, recently I have rooted my phone using the toolkit. The current recovery I have is TWRP. I wanted the root in the first place to be able to use xposed. However, it wont work, Whenever I try to install the update or new version it force reboots my phone. Also I found out I cannot update my software! I tried unrooting using the unroot option on SU but it was only temporarily. I want a permanent unroot and back to stock.
Android version : 4.4.2
Software number : 1.12.502.18
I downloaded my stock image from http://forum.xda-developers.com/showthread.php?t=2701376 and the toolkit from http://forum.xda-developers.com/showthread.php?t=2699065
I tried to flash it using the toolkit but it gave me an error when I tried to flash it. I don't recall correctly but it said something about a remote error right when it was sending the image over. Honestly I do not want to do it again to see what it said in fear of bricking my phone. So I will try to be as detailed as possible.
When I downloaded the image it said something about the name not being the original one. When I first tried flashing the stock ROM with the original name when I download it"stock recovery 1.12.502 recovery.img" it (the toolkit) gave me an immediate error of not being able to select it. So I renamed it to "recovery.img". I tried again and it actually was in the process of flashing. THen the error showed up as said above. Someone please help me. Thank you.
Update
So i just downloaded a different image. I flashed it successfully! I am currently rebooting from the original recovery! Currently I am on the htc one loading screen. It's been a couple minutes, hopefully I did not brick it...
NOPE! I successfully returned to stock! ANother issue...I still have root access! How can remove SU? I tried the unroot option in the app but I am still rooted after reboot...
UNROOTED. Sadly SU won't delete...but at least I'm unrooted and can update now.
Sent from my HTC One_M8 using XDA Free mobile app
helpmeunrootmyphone said:
UNROOTED. Sadly SU won't delete...but at least I'm unrooted and can update now.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know if the app is that big of a deal to you, but if it is, your options are...
1. Try factory reset in settings (may or may not work)
2. Reflash TWRP and flash the SuperSU.zip again than do a full unroot in settings.
3. Reflash TWRP and flash stock Sense ROM
Also, I made a guide in general which will help you fully return to stock. To begin the guide, you will need to be unlocked, rooted, and S-Off. That guide will help you hide the tampered and relocked banner.
If you don't care about the banners and the SuperSU app, it's probably not worth the effort and time.
Good luck.
Sent from my HTC One_M8 using Tapatalk
So you had an issue with Xposed, and you solution was to unroot? Wouldn't it have made more sense to troubleshoot the xposed problem? If you bothered to unlock the bootloader and root in the first place, IMO unrooting is a step backwards.
I'm also not a big fan of applying OTAs to a modded device. Yes, you cannot install official OTA updates on a modded phone. In particular, if stock recovery is not present, as its required for the OTA to install. If you want the latest software, just wait until the rooted version is posted in the Development section. Custom ROMs based on the 1.58 update started to be posted one day after the OTA started rolling out; and the stock rooted version was posted only 2 days after OTA release. For some people, getting it from here may even be faster than waiting for the OTA! That's pretty much how it goes. As long as there is developer interest in the device, you can rely on the latest software being available very quickly in the Development section.
The stock AT&T software is garbage anyway. I can't stand the amount of bloat, gimped features (WiFi hotspot) and other AT&T meddling. I don't understand why anyone would prefer this over other options. Software updates are always going to go to the international version first, anyway (AT&T is notorious for delaying updates for "testing"). What are you really getting with the 1.58 update? Extreme Power Savings mode, and a few other fixes? International M8 has had EPS mode for some time now.
---------- Post added at 09:31 AM ---------- Previous post was at 09:17 AM ----------
helpmeunrootmyphone said:
I downloaded my stock image from http://forum.xda-developers.com/showthread.php?t=2701376 and the toolkit from http://forum.xda-developers.com/showthread.php?t=2699065
I tried to flash it using the toolkit but it gave me an error when I tried to flash it. I don't recall correctly but it said something about a remote error right when it was sending the image over. Honestly I do not want to do it again to see what it said in fear of bricking my phone. So I will try to be as detailed as possible.
When I downloaded the image it said something about the name not being the original one. When I first tried flashing the stock ROM with the original name when I download it"stock recovery 1.12.502 recovery.img" it (the toolkit) gave me an immediate error of not being able to select it. So I renamed it to "recovery.img". I tried again and it actually was in the process of flashing. THen the error showed up as said above. Someone please help me.
Click to expand...
Click to collapse
Why do you need to use the toolkit at all, to flash recovery? Flashing recovery is a single fastboot command. Easy.
The toolkit adds unnecessary complication; and I've seen them cause errors when doing it "manually" works just fine. The toolkit might not be the problem in your case, but we would never know unless you try to do it manually.
If you really want to flash stock recovery (not my personal recommendation), I would start by wiping cache and flashing recovery with fastboot. I've seen maybe dozens of cases where issues with flashing a recovery was solved simply by wiping cache:
fastboot erase cache
fastboot flash recovery "filename.img"
I am having the same issue as above using the same build file from the link given in the other thread. However, whenever I am in Bootloader, the computer or terminal does not recognize my device.
1.12.502.18
Anytime I try to use the toolkit or manually through the command line, it gives me "unc paths are not supported" or "device not found". It is the same for both Bootloader and Recovery. My original problem was the person I bought it from had root on it so I decided to wipe the OS without backing up and now cannot get the Stock Recovery ROM or any other Custom ROM to install on the phone. I have also tried the SD card method and that brought up an error as well resulting in "failed."
Any help would be appreciated as the phone as it sits right now does not have any OS on it so it is stuck on the HTC Boot up screen.
Thanks in advance for those that can help.
Greetings, fellow Mega-Maniacs!
I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.
I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).
The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.
I'm in for $10 at the moment, and I'll piss away more if needed down the line.
Who else is in? LETS GET THIS DONE, PEEPS!
Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
kmt5150 said:
Greetings, fellow Mega-Maniacs!
I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.
I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).
The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.
I'm in for $10 at the moment, and I'll piss away more if needed down the line.
Who else is in? LETS GET THIS DONE, PEEPS!
Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
Click to expand...
Click to collapse
In for at least $20.
Put me down for 2 bucks.
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
DarkAngel said:
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Click to expand...
Click to collapse
Bootloader is locked
So no recovery flashing
Sent from my GT-I9205 using XDA Free mobile app
Grarak said:
Bootloader is locked
So no recovery flashing
Sent from my GT-I9205 using XDA Free mobile app
Click to expand...
Click to collapse
Well technically all bootloaders are locked (except for the few that aren't) but I take it AT&T is wanting/trying to join the band wagon with Verizon and locking the bootloaders indefinitely by encrypting them on all the devices they can now.
Sorry then, my method will not work straight forward. Good luck. :good:
DarkAngel said:
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Click to expand...
Click to collapse
Believe me, we have tried it all. I have tried a process similar to this and when the phone got done with all the flashing and went to boot up, I got a prompt that said 'We have detected software not approved for use by AT&T. Please take your phone to an AT&T store for assistance.' It also says Secure Check Failed: Kernel. I had to send my phone to sammy to get it fixed since I tripped a few flags. Should be back by Friday the 10th.
Possible to use this method with 4.4 kernel from mega?
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
jstinger9489 said:
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
Click to expand...
Click to collapse
Will definitely try this again when my phone gets here tomorrow and post updates...
jstinger9489 said:
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
Click to expand...
Click to collapse
Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."
UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
kmt5150 said:
Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."
UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
Click to expand...
Click to collapse
Have you tried towel root
http://towelroot.com/
BarakOsama said:
Have you tried towel root
http://towelroot.com/
Click to expand...
Click to collapse
Have YOU tried towelroot?
Or have you not read any of the many theads on the subject?
Sorry, not trying to be rude, the same thing has been said so many times
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Can anyone send me boot.img of ATT KK rom?
captemo said:
Have YOU tried towelroot?
Or have you not read any of the many theads on the subject?
Sorry, not trying to be rude, the same thing has been said so many times
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
My bad..
Alright.
To summarize for people who haven't paid attention. Phone was bricked in a last ditch effort to flash back to 4.3 because the 4.4 update made my phone run like s#it. I also have an S4 Active and the service sucks harder than it already did. The 4.4 update makes the S4 drop out constantly and the battery life blows. Samsung told me to run kies in download mode to get it back to 4.3 I did and BOOM, now phone is fu©k!ng bricked and they won't fix it, claiming it's 'rooted' because the kernel says it's version 3 when it's supposed to be at 4 for kitkat. Fu©k!ng duh, you jerks made me flash it back. I am personally never buying another samsung product again because their customer service was horsesh!t. I happen to have a sammy tv, blu ray, home theater and 2 of their former 'top end' phones, but now I'm ditching them. They can lick my scrotum for all I care anymore.
end rant, back to music.
SCH-R960
I have the US Cellular Galaxy Mega SCH-R960 also updated to 4.4.2 out of the box. I am in for some bucks if you can apply this to my version also the baseband number is R960TYUBNF1, I will send you whatever info you need from the phone. Lets get this done! Thank you!
MeatHammer311 said:
I have the US Cellular Galaxy Mega SCH-R960 also updated to 4.4.2 out of the box. I am in for some bucks if you can apply this to my version also the baseband number is R960TYUBNF1, I will send you whatever info you need from the phone. Lets get this done! Thank you!
Click to expand...
Click to collapse
Can you make a complete firmware dump and compile a .PIT file?
No root.
I do not have root so I can not do those things. If there is a way without root please point me in that direction. Thanks
MeatHammer311 said:
I do not have root so I can not do those things. If there is a way without root please point me in that direction. Thanks
Click to expand...
Click to collapse
sure you can
use heimdall
and can anyone send me the boot.img now?
I don't even think you guys want root if you're not even trying to help
Grarak said:
sure you can
use heimdall
and can anyone send me the boot.img now?
I don't even think you guys want root if you're not even trying to help
Click to expand...
Click to collapse
tell me how to get it any you will have it 1 before 5pm today est.
also here is the pit file you asked for. I used it to unbvrick my phone a few times with odin.
ita for the at&t version
I have an at&t variant HTC m8, I recently stitched to cricket wireless. SIM swap went fine. I've been wanting to gain root to remove att bloatware. I'm on android version 5.0.2. My main issue is I've gotten nowhere unlocking boot loader using a pc. Tonight I resorted to using kingroot from Google play,which worked on third attempt. However supersu said it needs an update.
So basically I'm lost and trying to find away to gain root without a computer if possible.
I've never used kingroot. What happens if you try to update the root binary?
May be a bit irrelevant. I think you'll need to unlock the bootloader to do what you want (delete bloatware). I don't think kingroot alone will get it done. Reason being, you can't modify the system partition with root alone. You need kernel mod wp_mod, which is flashed with custom recovery TWRP. And you need an unlocked bootloader to flash custom recovery.
What issues did you have exactly when trying to unlock the bootloader?
I believe my main issue was that my pc is out of date running an unauthorized widows 7 lol. I was unable to obtain adb or any twrp files to unlock boot loader hence my attempt at a one click type solution. I think I'm going to read up more and try the whole process over this weekend, but any tips guides or instructions would be helpful. The more I have looked into this the more conflicted things have become.
Lewis715 said:
I was unable to obtain adb or any twrp files to unlock boot loader hence my attempt at a one click type solution.
Click to expand...
Click to collapse
Not sure what "unable to obtain adb" means if you don't explain what happens exactly, where you are trying to get the files, etc. So all I can do is assume, and hope that I don't suggest you do things you already tried.
If you want an adb/fastboot installer, the following should work, and decently up to date: http://forum.xda-developers.com/showthread.php?t=2317790
Otherwise, there are other adb installers if you just type "easy adb" into the XDA search function.
No such thing as TWRP files that can help you unlock the bootloader. By definition, you can't install custom recovery until the bootloader is unlocked, and TWRP is a custom recovery. So nothing can be done with or by any TWRP files until you unlock the bootloader.
Lewis715 said:
I think I'm going to read up more and try the whole process over this weekend, but any tips guides or instructions would be helpful. The more I have looked into this the more conflicted things have become.
Click to expand...
Click to collapse
Again, can't really help with what is "conflicted" unless you give some specific details.
Its understandable that a lot of the threads may be confusing, as the info is often outdated. This is getting to be an old device, and a lot of folks that wrote the various guides have moved on, and not updating the guides.
The following is a pretty good AT&T specific guide: http://forum.xda-developers.com/showthread.php?t=2799796
But as mentioned, some things are outdated:
1) The driver package is old. You can get updated drivers by downloading HTC Sync from the HTC website. After installing (which will also install HTC drivers) you can uninstall Sync, but keep the drivers; if you don't want Sync (but I haven't had any problems keeping it).
2) I believe the Dropbox link for adb installer is dead, but I already gave an alternative above.
3) The TWRP version is really old, don't use it! Get TWRP 3.0.2 from here: https://dl.twrp.me/m8/
The exception might be in the stock Android version on your phone is old, but if you tell me what it says for OS number on the bootloader screen, I can advise more specifically.
4) TWRP version is old, again, don't use it! v2.76 is the latest "stable" version, and you can get it here: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
Everything else in the guide should still apply.
Vomer's guide is also a good one:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Again, the TWRP version is out of date (use the current one linked above).
You only need to do Sections 0 and 1, as the remainder of the guide (S-off, SuperCID) doesn't apply for what you are doing (unlock bootloader, custom recovery, and root).
Also, highly recommended to make a TWRP backup of the stock ROM, before you root.
After root, flash wp_mod with TWRP to enable system partition changes to stick (and deleting bloatware is a system change). What wp_mod depends on your Android version. But for Marshallow, the wp_mod can be found here (you just need the zip wp_mod, not the whole ROM): http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Thanks for the help I'll give it another try, honestly have no real need to mess with device. I know the phone is old but I still have it and it works better than others I've had.
Lewis715 said:
Thanks for the help I'll give it another try, honestly have no real need to mess with device. I know the phone is old but I still have it and it works better than others I've had.
Click to expand...
Click to collapse
Of course, the vast majority of us don't have any real need to mess with the device. But we do, nonetheless!
I recently managed to snag one of these up at a local walmart recently (well, 2 actually) - So I would share my experience with the software aspects I have dealt with so far.
Upon opening the box, I removed the NanoSIM (before even powering it up) and gave the device a full charge - no setup yet or anything.
I then went through the initial setup, skipping everything - not signing into Wi-Fi, or added my google account. The system was on B130 or B140, I can't recall now. I enabled developer settings, enable usb debug and checked OEM Unlock (for bootloader). I then connected it to my PC (I already had the proper drivers installed, and Minimal ADB and Fastboot) and proceeded to unlock the bootloader via the official code from Huawei. This of course gives you the warning that the phone is not secure, every time you power up the phone from fully off (or restart)
Now that the bootloader was successfully unlocked, I installed TWRP from the thread "[TWRP]Unofficial[5/21/2017]huawei ascend xt" by madvane20 using Fastboot. This was perfectly successful. Upon first load of TWRP I swiped to allow modifications.
Once in TWRP I copied the B180_Full_Update.zip from "[Guide]Huawei Ascend XT - How to update from any version up to B180 after rooting" by clsA - to a 4GB MicroSD Card that I put in the phone. I mounted system and cust, as it instructs in the thread - then proceeded to do a factory reset, format data from within TWRP (I might have done an advanced wipe too, and checked everything but the external SD, but I can't quite recall) and then did a reboot directly back to recovery.
I then proceeded to make sure that system and cust was mounted again, and installed the B180_Full_Update.zip - wiping dalvik/cache after. Then I did a standard reboot system, but the phone failed to boot. It just stopped at the unsecure warning, where you can press power (or wait) to boot anyhow. It would respond to me pressing power, but not go past that part. I was slightly concerned at this point, but lucky for me a long press of the power button and holding volume up - took me back to TWRP. So all was not lost.
I then decided to fully wipe everything again - following the previous steps I mentioned - and this time install the SR2-SuperSU-v2.79-SR2-20170103215521.zip from the thread "AT&T Huawei Ascend XT H1611 Feb27, 2017 update all things Root and TWRP (guide)" By powerserge1 . This was installed immediately after the Rom zip. Then I wiped dalvik/cache and reboot. This time the phone did boot as described (AT&T logo and a few automatic reboots, before actually getting to the setup screen) - I was then on B180 with SuperSU installed. Unfortunately, wifi was not working!
So at that point I decided to flash the boot.img (inside the boot.zip) at the bottom of the first post on the thread "[Rom][11thMay]Ascend XT - Swift&Fast Slim B160/b170/b180 aio" By madvane20. I did this with my PC via Fastboot. At this point the Wi-Fi was fixed. Unfortunately while SuperSU was installed ( and I ended up updating it via Play Store) - Root was not working (tried root checker from the play store), and the SuperSU program was not actually functioning properly. But other than that the phone seemed fully functional, and up to date.
I should state now that I bought this phone just to use it as a cheap tablet (Wi-Fi only), I do not have AT&T Service - and did not try and unlock it. So I cannot speak to how it performs as an actual cellphone - Service quality, service features etc.
Of course, I felt a little uneasy about the phone working fine - but not correctly rooted. I don't really need root for my uses, but it's what got it actually booting in the first place, so I figure I may as well know it is working. So here's my last step...
I just simply reflashed the B180_Full_Update.zip in TWRP. Mounted everything, full wipe of everything and rebooted back to recovery - before flashing of course. I did not reflash SuperSU or mess around with the boot.img etc. Just a davlik/cache wipe before rebooting the system. This time the system booted fine (AT&T logo and a couple resets, like before) and wifi was working right off the bat. I was at B180 still (obviously), and no signs of root or SuperSU. This is fine by me.
SO after all of that, it seems I am on a stock (unrooted, all bloat) B180 version (from B130 or B140, no other versions in between). Updated fully via unlocked bootloader, and various software. I have not tried to root again, because I don't need it. I just do the basic debloating that android natively allows, disabling all the AT&T stuff and various built in apps I wont use.
Hopefully this will be some help to anyone following the same path that I have, or currently in any of the hangups I was in.
Also, for anyone trying to replace the Huawei Home Launcher with something like Nova Launcher (recommended) - be sure to go to Settings/apps/Huawei Home/Open by default then clear defaults. This will allow you to select a new default launcher.
Feel free to ask any questions, and I will help as best as I can!
Good outline! It's not all too hard to get going, most of the hassle is tweaking EMUI.
As far as your problem with supersu... Supersu, and magisk as well, work by patching the boot img - so when you flashed the default boot files, you uninstalled the part of supersu that does the work (though not the management utility that provides its interface). Also take care not to clear cache/dalvik immediately after installing magisk or supersu, as their installers often use it as a workaround to inject their system files. My advice: flas osm0sis's unSu script (forum/google search), reboot, reboot into twrp, reflash default boot img, clear cache/dalvik, flash supersu, and then reboot (can reboot back into twrp to wipe cache/dalvik again if you want, just verify supersu is working first).
Edit: use the most recent flashable version of supersu from its thread - installs aren't device-specific
Thanks for reading, and for the insightful reply - that does shed some light on things for sure.
I'm still not really interested in rooting the device, but if I decide that I need to - that should sort me out. I just have to make sure I reinstall SuperSU from TWRP, if I flash that stock (I'm guessing) boot image..
My main problem was that I wanted to get it the phone up to the latest software version, and I don't have an active AT&T SIM. Well, actually now that I think about it maybe I could have just used the gophone sim that was installed in the phone... hah! I am no stranger to flashing ROMS/Recoveries etc. so I didn't mind having to go manual to get the phone up to date. This phone is blessed in that you are able to unlock the bootloader - just sucks that I had to, just to get it on a later version of official software. I like keeping my devices stock, as much a possible - provided it meets my needs in that form. Obviously if It is what it takes to make a device usable, or bring it up from a software update abandoned state - I will use Custom ROMs, and ROOT features where needed. I try not to even waste my time with devices like that though, unless it is acquired for very cheap or free. There are just so many other choices out there, and the used market is very good to me.
I guess the thing that escaped me while doing research to start on this phone, was how best to get to the latest stock B180 software version - altering as little as possible to get there. The only direct solution that I found assumed (or required) that you were also rooted, and I didn't think about that in the right way. I just assumed that it wouldn't matter that I was not, and that a bigger problem might be that I was jumping a few software versions. I'll admit I kinda skimmed over that part that said "Also some roms may need to have SuperSU flashed after the Rom or the phone may not boot the first time after the upgrade." I just figured I didn't need root, so I didn't have to worry flashing Super SU. It makes sense now, due in no small part to your explanation!
I wonder if (starting at stock bootloader unlocked B140) I could have just flashed that B180 full update zip from TWRP, and then PC fastboot flashed that boot image - forgo flashing superSU in TWRP - and then be good to go (Wi-Fi Working as well)? Assuming I was not interested in being rooted of course. I'm guessing not, and I'm not sure why.
As a follow up... I started working on the other phone I bought - brand new, on B140 Software Version.
Unlocked bootloader > flashed TWRP > full wipe/format everything > flashed B180 zip > and fastboot flashed boot image - presto change-o! Stock B180 with wifi working fine (no root, as desired). Still have the unlocked bootloader message upon power on, but that's unavoidable. This is pretty much the most direct method for manually updating to the latest software version.
I also used DC-Unlocker Successfully on both phones for about $4 USD each.