and i went on this link below
[How To] Flash ICS ROMs with S-ON Unlocked
I'm assuming you have
•Fastboot set up as a PATH, or copied to the folder you are extracting boot.img to
•HTC Drivers installed
•Clockwork Recovery
i have the drivers installed but i dont know the path and its not giving me details and to make it easyier to me i put everything on my desktop so please help me out here cause im about to sell this device and buy myself a g2 or g2x or a samsung android phone i really like bulletproof rom installed bad all i need for help is get CWM on this phone then i can handle it from there thanks.
you can download rom manager from play and install cwm
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You at least have to be unlocked and rooted. You're obviously not rooted, yet.
see
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me
crimedave1987 said:
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me
Click to expand...
Click to collapse
Have you pushed Superuser from a PC to the phone via USB? After that you can load CWM from ROM Manager.
Hastily spouted for your befuddlement
crimedave1987 said:
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me
Click to expand...
Click to collapse
Just being unlocked is not the same as being rooted. You need to be Unlocked AND rooted to install CWM through Root Manager. You're only half of that.
Coug76 said:
Have you pushed Superuser from a PC to the phone via USB? After that you can load CWM from ROM Manager.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
nope im having trouble doing that i need help on that part
With an unlocked bootloader I simply copy the fastboot and adb files, as well as whatever recovery image I want to flash and push the recovery via fastboot... however if you aren't confident in your skills with the command prompt or fastboot there is always the all-in-one toolkit for the MT4GS that can be downloaded from its own thread in the dev forums (I don't have the link handy but it seemed to work for me on my sister's mt4gs).
I'm having trouble flashing CWM from the market as well. I've rooted (or at least I think I have) via Hasooon2000's tool and the superuser icon shows up in my drawer but when I try to run it I'm never prompted with the usual permission request, just the permission error that OP posted. I am also unable to install anything like Busybox or ROM Toolbox. It seems like the root just wasn't properly set up but none of the methods I've found actually work. I have tried to redo the rooting process, but to no avail.
I flashed CWM from Hasoon200's tool too, and can boot into it, however when I try to take a backup it just goes to a screen with the CWM logo in it and doesn't do anything. I have to pull the battery to get it to reboot.
Never had this much trouble with rooting or flashing a recovery before, but if anyone can help I'd appreciate it.
I'd say do a flash of CWM via adb. Then install Superuser through CWM using a zipped Superuser. Worked flawlessly for me.
yupThisIsMyName said:
I'm having trouble flashing CWM from the market as well. I've rooted (or at least I think I have) via Hasooon2000's tool and the superuser icon shows up in my drawer but when I try to run it I'm never prompted with the usual permission request, just the permission error that OP posted.
I flashed CWM from Hasoon200's tool too, and can boot into it, however when I try to take a backup it just goes to a screen with the CWM logo in it and doesn't do anything. I have to pull the battery to get it to reboot.
Never had this much trouble with rooting or flashing a recovery before, but if anyone can help I'd appreciate it.
Click to expand...
Click to collapse
Are you using the trackpad to select things in recovery? All of my other phones used power while in recovery to select things but the doubleshot uses trackpad to select
Sent from my myTouch_4G_Slide using Tapatalk 2
I'm of two different schools of thought here - my first thought is bad download of CWM... Honestly I'd just read up on fastboot flashing the recovery image and do that to ensure a good root. However as noted above the trackpad select did throw me off at first.
Sent from my myTouch_4G_Slide using XDA
OK, it looks like I don't actually have S-Off and I've got the newer Hboot which, from what I can tell, prevents me from using this method and the only two ways to do this seem to involve either doing some crazy stuff with wires or flashing stuff without taking a backup first. Both of these methods make me very nervous, especially since as far as I can tell there is no way to use anything like Odin or RSD Lite with this phone to restore it in case something gets messed up.
If anyone has a way I can take a backup before flashing a ROM or, better yet, has a way to restore the phone completely in case something goes awry that would be awesome.
Update: Yeah, looks like it was the trackpad thing preventing me from doing this properly. Totally bizarre considering the fact that I was able to select things just fine using the volume buttons but when I hit power (which selects on most devices), it didn't work right.
Thanks for helping me get past this hurdle everyone! Hopefully I can figure out how to get s-off.
Edit: Update - I flashed a ROM that already had root and now that works too. Good enough for now, I'll wait for a less scarey method to get S-off. I'm not about to start messing around with wires.
Related
ive tried everything to fix this error. ive only seen 3 other post about this error, but nothing in them is helping.
i rooted my fender mytouch, got to the point where the magic rom is on and no touch screen, reboot and flash the radio and HBOOT of the stock fender rom, but Amon Ra's recovery.img always gives me this error. is there any other recovery.img i could try maybe?....
which version recovery u using?? g or h?
i am using 1.6.2G
DaemonAshra said:
i am using 1.6.2G
Click to expand...
Click to collapse
You have the right one but I have never seen this error before. It wont let you flash any roms? Considering if you didnt have a touch screen you didnt flasha rom for our phones. We only have 3 real roms lol
crypysmoker said:
You have the right one but I have never seen this error before. It wont let you flash any roms? Considering if you didnt have a touch screen you didnt flasha rom for our phones. We only have 3 real roms lol
Click to expand...
Click to collapse
here is what it looks like on command prompt.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i could only find this error on G1 forums and even then i think there was only 2 occurrences on other sites. i just dont understand why only the recovery file would be the one that doesnt work....
the HBOOT and radio i flashed went on the phone perfectly, but the recovery, even the older unperfected ones wont flash . they all give this error....
The only error I get is when I try to perform a Nandroid backup + ext or a Bart backup. Normal Nandroid works fine. I dont think we have A2sd working but I would love to see that option come back and not have to push via ADB
at the moment, im on the Magic's home screen with no touch screen drivers so i know my phone isnt bricked or anything. all i really need now is a recovery.img that will write to the device.
a little more detail about it: when i was flashing the files to the phone in fast boot. i did see that the green status bar loaded when tranfering the recover.img to the phone and it did show the red status bar like it was trying to install, but the bar never filled and after about a minute, it disappeared and the image update error showed on the command line.
im pretty much just trying to give every detail i can and keep trying different .img's to see if something fixes this weird problem.....
So is this before or after reflashing the stock SPL/radio? It looks like your trying to flash the recovery after putting the locked spl back on.
If not, I suggest trying it from the beginning.
crypysmoker said:
So is this before or after reflashing the stock SPL/radio? It looks like your trying to flash the recovery after putting the locked spl back on.
If not, I suggest trying it from the beginning.
Click to expand...
Click to collapse
this is when im trying to put the fender stock SPL/Radio in fastboot after getting the htc magic rom with no touchscreen drivers on it. i am following the steps for flashing using the goldcard method and ADB from the Unlockr's 1.2/fender rooting tutorial, and i got the radio.img and HBOOT.nb0 flashed on there successfully, but only this recovery.img isnt flashing.
i swear. this is the like the last hurdle before getting the whole thing done, and its the only thing that didnt work perfectly. everything else was going great.
Gerr1985 said:
The only error I get is when I try to perform a Nandroid backup + ext or a Bart backup. Normal Nandroid works fine. I dont think we have A2sd working but I would love to see that option come back and not have to push via ADB
Click to expand...
Click to collapse
Nandroid+Ext will fail unless there's something there to backup on an ext partition. A2SD works fine on the cm port at least, in fact, it automatically works, which I discovered after deleting my ext2 partition and discovering most of my apps were now broken links.
Problem is if you flash the hboot first you are blocking anything going through fastboot. Try booting the recovery rather then flashing. . Fastboot boot recovery. Img. . If it doesn't load or gives same error start from scratch. Do recovery first. Reason touch didn't work us because we only have 3 real ROMs to use noted by fender/1.2
ignore this. sorry.
crypysmoker said:
Problem is if you flash the hboot first you are blocking anything going through fastboot. Try booting the recovery rather then flashing. . Fastboot boot recovery. Img. . If it doesn't load or gives same error start from scratch. Do recovery first. Reason touch didn't work us because we only have 3 real ROMs to use noted by fender/1.2
Click to expand...
Click to collapse
oh okay. i will try this when i get home. i am at work at the moment and will be for the next 6 hours.....
just asking, but does it matter the order of flashing? like if i did radio, then recovery, and hboot last? or i guess it would be best to try loading the radio and hboot, then booting recovery...
oh okay. i will try this when i get home. i am at work at the moment and will be for the next 6 hours.....
just asking, but does it matter the order of flashing? like if i did radio, then recovery, and hboot last? or i guess it would be best to try loading the radio and hboot, then booting recovery...
Click to expand...
Click to collapse
not sure... but watever u do make sure u flash RADIO before HBOOT/SPL...if not youll end up with a brick
ceas909 said:
not sure... but watever u do make sure u flash RADIO before HBOOT/SPL...if not youll end up with a brick
Click to expand...
Click to collapse
this is important to know. thank you for that info. i will flash radio, hboot, then try booting recovery. i will report back on the results.
Try flashing an older version of Amon Ra. I think when I rooted I used v1.5.2 and then upgraded to 1.6.2.
i bricked it. for the record, i tried that version of amon ra but it didnt work either. i ended up bricking it by trying to load the recovery.img before the hboot.
i bricked it. for the record, i tried that version of amon ra but it didnt work either. i ended up bricking it by trying to load the recovery.img before the hboot.
Click to expand...
Click to collapse
did u even get a chance to flash hboot?...if you did and can still get into hboot.. grab the stock mt3g 1.2 sappimg(search for it here on xda) and flash it via hboot..
ceas909 said:
did u even get a chance to flash hboot?...if you did and can still get into hboot.. grab the stock mt3g 1.2 sappimg(search for it here on xda) and flash it via hboot..
Click to expand...
Click to collapse
no i didnt. hboot gave me this error message and i couldnt get it to flash. i dont even know if its fully bricked forever or not. i just dont have the knowledge to fix it.
when i plug it in to the charger. after a little while, i get the orange light that its charging, so its probably not completely dead.
if it doesn't turn on its gone...
Sent from my T-Mobile myTouch 3G using the XDA mobile application powered by Tapatalk
Hi all,
so I've been reading around here for a few weeks now. Found a few guides on rooting the Desire S and tried to get basic orientation.
Now I'd like to discuss my particular situation for a bit with you guys, before I attempt to actually do the job on my phone.
There is a slight difference between where I'm finding myself and where all the rooting guides seem to aim:
I bought my Desire S already S-OFF'ed.
You can see my exact specs at the lower end of this post.
As it appears, AlphaRev and Revolutionary are supposed to be used with S-ON devices. I'm not sure what would happen if I run these tools with my S-OFF device.
GingerBreak doesn't work with HBOOT-0.98.0002. So that won't help me either.
The most promising method i found so far is the Temproot + Revolutionary method by Silver Bullet, which has been tested on a device with the exact same Hboot and ROM build as mine, with the only exception, that I am on S-OFF.
Today I've been successful in achieving temporary root access, using the commands from Silvers thread. (I got the # prompt.)
Sof far, so good. Now I've got and S-OFF'ed device with temporary root access possibility.
Silver proposed this in a personal message (hope it's ok I'm posting it here):
You could try to get temporary root access using the commands I have posted in my guide. If you get the "#" prompt then you have root access, so you could use dd from the command prompt to a) backup your current HBOOT, just in case, and b) flash the recovery manager of your choice.
With the recovery manager in place, you'd be able to flash whatever rom you like.
Please note that I have no means to test this procedure on my own!
You should take your risks if you dare!
Now I don't understand how I "use dd from the command prompt to a) backup your current HBOOT, just in case, and b) flash the recovery manager of your choice."
So what do all of you think about this approach? Do you see it as safe? If not, what could possibly be a safer method? Any other suggestions/comments?
Also, could anyone kindly direct me to some info about how exactly do I flash a recovery in this setup?
Thanxalot!
since you are already s-off i think you should be able to install a custom recovery on your device(im not sure about this you may want to wait for someone else to confirm this just to be safe)
once you have a custom recovery you can install a custom ROM or a prerooted stock ROM to gain ROOT access
try this recovery
this is the link to the DS index thread for easy access to more useful threads
If you are s-off, you have fastboot so you can flash a recovery with adb. And flash a new rom
Sent from my HTC Desire S using XDA Premium App
kartkk said:
since you are already s-off i think you should be able to install a custom recovery on your device(im not sure about this you may want to wait for someone else to confirm this just to be safe)
once you have a custom recovery you can install a custom ROM or a prerooted stock ROM to gain ROOT access
try this recovery
this is the link to the DS index thread for easy access to more useful threads
Click to expand...
Click to collapse
Yea, I've been thinking in the same direction.
So there are two possibilities I can think of right now, as to how to install 4EXT recovery.
1) Download "4EXT Recovery UPDATER" to my phone -> then -> Enter temporary root state using adb -> then -> download & flash 4EXT recovery automatically using "4EXT updater"
or
2) Download "4EXTRecovery_v2.1.0_saga.zip" to computer -> then -> enter temporary root state using adb -> then -> flash "4EXTRecovery_v2.1.0_saga.zip" from computer using fastboot.
Agreed? Which one seems more reasonable to you guys?
Could someone experienced please confirm that I'm getting this right?
Flashing 4EXT recovery via fastboot:
1) download <4EXTRecovery_v2.1.0_saga.zip>
2) extract the <recovery.img> file from that zip archive
3) run these commands: fastboot flash recovery recovery.img
Correct? Do I need to wipe something first or can I just flash right away?
Secondly, Silver was talking about first backing up my current Hboot using adb, before I attempt to flash the 4EXT recovery. Does anyone please know how to do this? Can't find it anywhere explained.
Thanks
You'll first need to download and extract the adb & fastboot links from my signature and esnure that you have the HTC Drivers installed on your PC (also in my links in my signature).
Then follow the instructions within the Flash CWM & su via fastboot link that's in my signature.
That will put CWM (clock work mod a custom recovery and make you root by installing the su (super user) )
I'd say follow this and then once you've CWM and are root simply install the 4EXT from the market and update recovery to 4EXT (again link in my sig).
Any question then fire away?
ben_pyett said:
You'll first need to download and extract the adb & fastboot links from my signature and esnure that you have the HTC Drivers installed on your PC (also in my links in my signature).
Then follow the instructions within the Flash CWM & su via fastboot link that's in my signature.
That will put CWM (clock work mod a custom recovery and make you root by installing the su (super user) )
I'd say follow this and then once you've CWM and are root simply install the 4EXT from the market and update recovery to 4EXT (again link in my sig).
Any question then fire away?
Click to expand...
Click to collapse
Ok, got you ben_pyett. Thanks for clear instructions.
So no way (or need) to backup hboot prior to flashing recovery?
And no need to enter temporary root state before flashing WCM?
Gonna give it a try.
mimirom said:
Ok, got you ben_pyett. Thanks for clear instructions.
So no way (or need) to backup hboot prior to flashing recovery?
And no need to enter temporary root state before flashing WCM?
.
Click to expand...
Click to collapse
You can always get the original HBOOT (recovery) back from a stock ROM RUU if and when you need, see link to STOCK ROMS in the thread DEV INDEX
you may be able to do it via temp root fr3vo and adb but I'm not 100% . Temp root - If you're S-OFF I don't think you need to, but be sure to flash correct verison of CWM (saga) or else there is trouble.
I downloaded the newest CWM (recovery-clockwork-5.0.2.0-saga.img) for saga from the Clockworkmod website.
Attempted to flesh it simply using fastboot. This is what I got.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So perhaps the next step could be 1) get into temporary root state 2) flash
Comments?
edit: Ok, I see now the difference - to do it via temproot + adb I need to work with android up and running.
mimirom said:
I downloaded the newest CWM (recovery-clockwork-5.0.2.0-saga.img) for saga from the Clockworkmod website.
Attempted to flesh it simply using fastboot. This is what I got.
So perhaps the next step could be 1) get into temporary root state 2) flash
Comments?
edit: Ok, I see now the difference - to do it via temproot + adb I need to work with android up and running.
Click to expand...
Click to collapse
was your device in HBOOT, FASTBOOT USB ?
How to start Fastboot USB mode:
Unplug USB
Turn the device off
Hold volume down button (HOLD IT) and press power
Hboot will start.
Wait for sdcard scan to complete.
Plug in USB cord connected to the computer
Press power ONCE and Fastboot USB mode starts
ben_pyett said:
was your device in HBOOT, FASTBOOT USB
Click to expand...
Click to collapse
Yes, it was. That's why I get the device listed when I do the <fastboot devices> command
I tried the same procedure also in hboot mode, but there I get a <waiting for device>
When the phone is in fastboot I get <FAILED (remote: not allowed)> now.
Thanks for your assistance ben_pyett. Appreciate it.
edit: So something changed, since I'm not getting the <FAILED (command write failed (Unknown error))> anymore, but now it's <FAILED (remote: not allowed)>
Ensure that you device has device has "Debug USB" enabled
Boot and then Settings->Applications->Development->USB Debugging = YES (tick)
and then try again
Unfortunately that's not the problem. The phone has been in debugging mode from the beginning. It also shows the <usb debugging connected> in status bar when I connect it.
I found an older thread where people seem to have been successful rooting s-off devices with superoneclick. Will read through it.
Thinking back to what I did after I'd Made my s devices s-off although I used xtc
Although first question, have you tried running ginger break? You'll find a link to it from within the root section of the http://forum.xda-developers.com/showthread.php?t=1146601DEV INDEX a sticky in that forum on the root sub section
Anyway what I did myself I've I was s-off was to Install a boot image that then enabled me to simply run one click, which gave me root.
http://forum.xda-developers.com/showthread.php?t=1105763 Link to boot image post
You find link the link to ginger break and super one click used with in the Dev INDEX within the root sub section
So try ginger break first and if that doesn't work, then boot image and super one click which is literally that easy
Once you're root simply download ROM manager from Android market and use that to install Cwm as it's only one click
Good luck
Swyped from my Desire S using XDA Premium
Great help, thanks!
I tried Gingerbrake a few weeks ago without success. A far as I know it doesn't work with HBOOT-0.98.0002. Some folks propose downgrading the hboot but I noticed that it's supposed to be dangerous. However I'll give it another try.
The one click method you propose looks good, thanks. I remember though that I tried to flash something using a "PG88IMG.zip" during my few initial attempts to get root, and my phone refused to read it from the sd card.
Would love to try it right away, have to leave though...
Cheers.
Hi ben_pyett,
it clicked! (pun fully intended)
I first flashed the boot image and then ran SuperOneClick.
I have SuperUser installed. RootChecker confirmed full root access. Right now Im doing a Nandroid backup from CWM recovery.
Loved to see that recovery screen again (I'm coming from Wildfire)
So thank you ben_pyett for your patience and willingness to offer not-just-sporadic support.
_______________________________________
There were slight complications occurring during the root process. Superoneclick hanged at step 6. After disabling USB debugging it showed a few more lines in the right window section and after enabling USB debugging again it finished the root procedure without further problems.
It seems to me that the phone now takes longer to shut down plus, more importantly, Wifi stopped working. It gives an error message on the Wifi tab in settings.
Actually the phone appears generally unstable now. It just gave me a <Tell HTC> notification with something like "the phone just recovered from an abnormal reboot."
Hope I can sort this out by flashing a new rom...
So far, so good. Go to bed now.
mimirom said:
Hi ben_pyett,
it clicked! (pun fully intended)
I first flashed the boot image and then run SuperOneClick.
I have SuperUser installed. RootChecker confirmed full root access. Right now Im doing a Nandroid backup from CWM recovery.
Loved to see that recovery screen again (I'm coming from Wildfire)
So thank you ben_pyett for your patience and willingness to offer not-just-sporadic support.
_______________________________________
There were slight complications occurring during the root process. Superoneclick hanged at step 6. After disabling USB debugging it showed a few more lines in the right window section and after enabling USB debugging again it finished the root procedure without further problems.
It seems to me that the phone now takes longer to shut down plus, more importantly, Wifi stopped working. It gives an error message on the Wifi tab in settings.
Actually the phone appears generally unstable now. It just gave me a notification with something like "the phone just recovered from an abnormal reboot."
Hope I can sort this out by flashing a new rom...
So far, so good. Go to bed now.
Click to expand...
Click to collapse
Now you have root you can get custom recovery and from there you can Custom ROMS, there are loads to choose from.
All the problems you report are fixable.....wifi fails as boot image is missing Wifi do modules, but a custom well resolve that, glad you got there in the end.
Ensure that you have Settings->Power->Fastboot set to OFF (un-ticked)
night
Can't root your desire s ? Me too...
smartceleron said:
Can't root your desire s ? Me too...
Click to expand...
Click to collapse
Well, no, I actually rooted it the way described in this thread... The thread is also labeled as "solved" now.
Did u try to follow the steps described? What are your specs?
Sent from my HTC Desire S using XDA App
S4 T-Mobile + 4.3 = "there is no su binary installed and supersu can not install it.
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?
no, there's no working root at this time.
Sent from my GT-I9505 using Tapatalk 4 Beta
Thank you for the info.
I have to say this, the speed improvement on 4.3 is very noticeable. I am back to CM10.1 and it feels slow in comparison...
beaver2233 said:
no, there's no working root at this time.
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
dotpage said:
Thank you for the info.
I have to say this, the speed improvement on 4.3 is very noticeable. I am back to CM10.1 and it feels slow in comparison...
Click to expand...
Click to collapse
How did you get back to CM10.1?
AlAmeri said:
How did you get back to CM10.1?
Click to expand...
Click to collapse
Flash it using a custom recovery
Me Gusta!
Me Gusta said:
Flash it using a custom recovery
Me Gusta!
Click to expand...
Click to collapse
So flashing ROM without root is possible?
AlAmeri said:
So flashing ROM without root is possible?
Click to expand...
Click to collapse
Directly from Android, no. You'll need root to do that. Just power off your device, when its turned off press and hold volume up, home and power at the same time. Flash from recovery.
fcknghst said:
Directly from Android, no. You'll need root to do that. Just power off your device, when its turned off press and hold volume up, home and power at the same time. Flash from recovery.
Click to expand...
Click to collapse
So Android 4.3 without root. I have a costume recovery, CWM, I could simply just flash a new ROM and it wouldn't brick my S4?
Sorry for the newbie questions but I'm coming from zero experience.
AlAmeri said:
So Android 4.3 without root. I have a costume recovery, CWM, I could simply just flash a new ROM and it wouldn't brick my S4?
Sorry for the newbie questions but I'm coming from zero experience.
Click to expand...
Click to collapse
Yup. Just do a wipe and flash whatever you like. As long as you have access to bootloader, and keep a backup it is very hard to brick your phone - Im new to samsung, but as i understand with Odin it is even harder to brick it.
On a side note, i had some issues getting it to mount /system - Turns out that it cant if the phone is plugged into the computer (i did a facepalm after trying ~3hours getting it to flash CM )
fcknghst said:
Yup. Just do a wipe and flash whatever you like. As long as you have access to bootloader, and keep a backup it is very hard to brick your phone - Im new to samsung, but as i understand with Odin it is even harder to brick it.
On a side note, i had some issues getting it to mount /system - Turns out that it cant if the phone is plugged into the computer (i did a facepalm after trying ~3hours getting it to flash CM )
Click to expand...
Click to collapse
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.
AlAmeri said:
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.
Click to expand...
Click to collapse
So you cant restore your backup, from before 4.3?
fcknghst said:
So you cant restore your backup, from before 4.3?
Click to expand...
Click to collapse
Exactly. I tried searching for stock firmware, couldn't find one. So I thought either I find a way to restore. Or flash an already rooted ROM. You see my dilemma.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dotpage said:
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?
Click to expand...
Click to collapse
Use Odin to reload TWRP, it happened to me too... Put phone in Download mode, use PDA option pointing to TWRP's file...
AlAmeri said:
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.
Click to expand...
Click to collapse
dotpage said:
Use Odin to reload TWRP, it happened to me too... Put phone in Download mode, use PDA option pointing to TWRP's file...
Click to expand...
Click to collapse
But I don't have TWRP. I use a CWM based recovery.
How does it work?
So I flash TWRP using odin, and then what?
AlAmeri said:
But I don't have TWRP. I use a CWM based recovery.
How does it work?
So I flash TWRP using odin, and then what?
Click to expand...
Click to collapse
In any case - Back up your current (working) installation - There will be a way to get root in the future. Now you dont have to worry about not being able to use the phone (since you have a working backup), and you can goahead and flash something else.
Dont bother installing different recoveries, they all work just fine - And TWRP wont be able to restore from a CWM backup anyways..
But I dont understand why CWM cannot access your former backup.
fcknghst said:
In any case - Back up your current (working) installation - There will be a way to get root in the future. Now you dont have to worry about not being able to use the phone (since you have a working backup), and you can goahead and flash something else.
Dont bother installing different recoveries, they all work just fine - And TWRP wont be able to restore from a CWM backup anyways..
But I dont understand why CWM cannot access your former backup.
Click to expand...
Click to collapse
That's actually genius. Don't know why I haven't thought of it earlier. Backup and experiment.
Thanks.
Chainfire is taking longer than usual. Its got me worried. I'm loving Stock Android, going to try flashing 4.2.2. Hopefully won't run into trouble.
If you find 4.2.2 vanilla(T-Mobile) let us know, I am looking for that ROM....
AlAmeri said:
That's actually genius. Don't know why I haven't thought of it earlier. Backup and experiment.
Thanks.
Chainfire is taking longer than usual. Its got me worried. I'm loving Stock Android, going to try flashing 4.2.2. Hopefully won't run into trouble.
Click to expand...
Click to collapse
dotpage said:
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?
Click to expand...
Click to collapse
dont know if this will work for you but here goes. i have a T999L (T-Mobile LTE S3) i have twrp installed on it and i have slimbean 4.3 official build installed on it, i had the same issue with getting 4.3 rooted but i got it figured out first make sure in the developer options you have superuser allowed by adb and apps.
( if you don't see developer options in your settings menu
go to :Settings>About Phone> click on your build number several times until you get a toast that says your almost a developer keep clicking until it says it has been enabled)
then you will use motoChopper to push the exploit to get the superuser.apk added to the system/apps folder once you do this it won't work as they have somehow allowed access for the expoit to push the .apk but not push the binary to the system/xbin folder.
now pull the SU binary out of the motoChopper folder on your computer and place in on your sdcard
boot into TWRP, mount the file system and copy it from your sdcard to the system/xbin folder and voila you are done, when you go to reboot your device from TWRP it will ask you if you want to fix the Superuser permissions just skip and reboot
( all rights thanks and so on go to the original developer djrbliss and i do not take any credit for his work, nor did i get permission to modify his work, i tried but got no response so i modded it for myself to use and i am now sharing, all i did was swap the Superuser.apk and SU binaries he used in his exploit.) @djrbliss if you would like this post removed just let me know and i will pull it!
not sure why the list showed up as 1 1 1 2 but i think you get the point
I'm not that experienced in this new htc development stuff nowadays, because it's been long time I havent browsed forums closely. Anyways a friend has this One SL phone, and somehow it's bricked and asked me to help him repair it, because I owned htc phone before and was more experienced (which I doubt now).
Here's the problem i'm facing and hoping someone could point me to some information where to start from. Device is S-On and haven't been rooted or bootloader unlocked or any thing else, its totally stock with stock recovery and rom. After powering the phone it boots ok, but when I get to lockscreen and try to unlock it it gives me some errors like : com.android.settings has stopped and beneath that message is another one which is hard to read because this one getting all the time, Unfortunately, System UI has stopped.
I tried to hard reset from bootloader because I cant get to recovery from there it gives me a sign and not getting any recover. So I only did factory reset several times, and clear data but that doesn't fix anything. I got some pictures of the error and bootloader screen if that can help anyone to give me some more information.
Btw i'm trying to find out what is the stock rom for this phone but can't find out how to get that information from a non fully working system. If that is possible I would flash stock rom and see if it will fix the problem.
I wrote a lot of text but I wanted to clarify the situation in my way.
Here are the pictures I took:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can unlock the device, flash a custom recovery and flash a stock rom.
If you are locked, you can do pretty nothing.
is the SIM card good?
old.splatterhand said:
You can unlock the device, flash a custom recovery and flash a stock rom.
If you are locked, you can do pretty nothing.
Click to expand...
Click to collapse
Do you mean locked like Sim locked or bootloader locked? If you mean Sim locked it is sim unlocked accepts all sim cards. If you mean bootloader how to unlock it can you guide me.
russellvone : It was without sim card inside when I made picture that's why it shows Emergency only.
Bootloader unlocked.
Go to www.htcdev.com and follow the steps there.
old.splatterhand said:
Bootloader unlocked.
Go to www.htcdev.com and follow the steps there.
Click to expand...
Click to collapse
Ok I followed the steps and get the bootloader unlocked It says ***UNLOCKED *** but under that I still have SHIP S-ON . Can I use any shipped rom to flash this device now or what should I do if you can help me out.
Now you have to flash custom recovery (TWRP recovery) with fastboot.
Look into my index thread, you can find a link to the newest TWRP there.
old.splatterhand said:
Now you have to flash custom recovery (TWRP recovery) with fastboot.
Look into my index thread, you can find a link to the newest TWRP there.
Click to expand...
Click to collapse
Im on your page and following the information to install TWRP 2.6.3 but there's written with red letters
"Only for k2u & k2ul!
Important: Recommended for hboot 2.21!" and i'm on hboot 2.00 does that matter?
Works also on hboot 2.00.
old.splatterhand said:
Works also on hboot 2.00.
Click to expand...
Click to collapse
Ok you helped me a lot till now. I finished TWRP and it works, im in the recovery now. Now what build can I flash or what to do to fix the phone.
For example this: http://forum.xda-developers.com/showthread.php?t=2254384
Don't forget to flash the boot.img with fastboot (see "How to install").
old.splatterhand said:
For example this: http://forum.xda-developers.com/showthread.php?t=2254384
Don't forget to flash the boot.img with fastboot (see "How to install").
Click to expand...
Click to collapse
This all information you gave me worked and the phone is working perfectly now.
Million thanks to you bro, i'm feeling happy knowing that in the world still exist people who are willing to help others, people like you. Thanks once again .
Any mod can update title to Solved, and maby a guide to someone in my situation
Glad, you've got it to work again.
Sorry if this question does not belong here, I'm a noob. A few days ago I was trying some things with the sunshine free apk and after a few minutes I got a message that said "congratulations now you have temp root", then I installed TWRP through google play, rebooted into recovery and it worked. At that time I did not try to install a Custom Rom through this method because I wasn't sure about it, my question is Can I install a custom rom doing with this method? (like the google play edition sensified rom)
coderch123 said:
Sorry if this question does not belong here, I'm a noob. A few days ago I was trying some things with the sunshine free apk and after a few minutes I got a message that said "congratulations now you have temp root", then I installed TWRP through google play, rebooted into recovery and it worked. At that time I did not try to install a Custom Rom through this method because I wasn't sure about it, my question is Can I install a custom rom doing with this method? (like the google play edition sensified rom)
Click to expand...
Click to collapse
I'm not really sure what to tell you. If you managed to install TWRP without getting S-Off and an unlocked bootloader (never heard of this) I would think you could flash a rom. However, I don't know if it would work for you or not. If the rom comes with a boot.img file, it would almost certainly fail to flash that part of the rom. You would need an unlocked bootloader for that to work. If the system part of the rom did flash, it might be nothing but headaches if it relied on the boot.img. I'm not even sure if the system would flash without an unlocked bootloader. My guess is probably but I think you might be in for a world of headaches if you do it. I would recommend just running sunshine and paying the piper . Maybe somebody else more knowledgeable than me can answer and tell you for sure. I'd tread lightly on this one if I were you. I just don't know for sure. All I know is that boot.img isn't going to succeed.
robocuff said:
I'm not really sure what to tell you. If you managed to install TWRP without getting S-Off and an unlocked bootloader (never heard of this) I would think you could flash a rom. However, I don't know if it would work for you or not. If the rom comes with a boot.img file, it would almost certainly fail to flash that part of the rom. You would need an unlocked bootloader for that to work. If the system part of the rom did flash, it might be nothing but headaches if it relied on the boot.img. I'm not even sure if the system would flash without an unlocked bootloader. My guess is probably but I think you might be in for a world of headaches if you do it. I would recommend just running sunshine and paying the piper . Maybe somebody else more knowledgeable than me can answer and tell you for sure. I'd tread lightly on this one if I were you. I just don't know for sure. All I know is that boot.img isn't going to succeed.
Click to expand...
Click to collapse
Thank you, then I'll have to buy the full version of app
coderch123 said:
Sorry if this question does not belong here, I'm a noob. A few days ago I was trying some things with the sunshine free apk and after a few minutes I got a message that said "congratulations now you have temp root", then I installed TWRP through google play, rebooted into recovery and it worked. At that time I did not try to install a Custom Rom through this method because I wasn't sure about it, my question is Can I install a custom rom doing with this method? (like the google play edition sensified rom)
Click to expand...
Click to collapse
I suspect you haven't accomplished as much as it sounds. I don't believe you can flash a custom recovery with s-on and a locked bootloader. When you ran sunshine, did you go all the way and pay for it or did you stop after gaining temp root? Temp root may allow something like the TWRP app (different from the actual TWRP recovery) to think it's done it's thing without the flash actually completing. When you say "it worked" do you mean you booted all the way into TWRP recovery?
cntryby429 said:
I suspect you haven't accomplished as much as it sounds. I don't believe you can flash a custom recovery with s-on and a locked bootloader. When you ran sunshine, did you go all the way and pay for it or did you stop after gaining temp root? Temp root may allow something like the TWRP app (different from the actual TWRP recovery) to think it's done it's thing without the flash actually completing. When you say "it worked" do you mean you booted all the way into TWRP recovery?
Click to expand...
Click to collapse
Yep, I installed the app from google play and then it asked me if I wanted to reboot into recovery so I did it. I was able to use TWRP but I didn't try anything because I wasn't sure.
coderch123 said:
Yep, I installed the app from google play and then it asked me if I wanted to reboot into recovery so I did it. I was able to use TWRP but I didn't try anything because I wasn't sure.
Click to expand...
Click to collapse
But you're sure that you still have s-on and a locked bootloader? What happens if you turn off the phone and then enter the bootloader (volume up + power) and enter recovery from there? Does it take you to TWRP or stock recovery.
cntryby429 said:
But you're sure that you still have s-on and a locked bootloader? What happens if you turn off the phone and then enter the bootloader (volume up + power) and enter recovery from there? Does it take you to TWRP or stock recovery.
Click to expand...
Click to collapse
Here's a picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, but if you enter recovery from hboot as in your picture do you actually go into twrp? I wonder if either the TWRP app (with temp root) was somehow able to boot twrp instead of flashing it to the recovery partition and booting to recovery or perhaps some previous owner flashed a spoofed hboot and you actually do have an unlocked bootloader but don't know it. Did you buy the phone new with this being the first time you've tinkered with it?
cntryby429 said:
Ok, but if you enter recovery from hboot as in your picture do you actually go into twrp? I wonder if either the TWRP app (with temp root) was somehow able to boot twrp instead of flashing it to the recovery partition and booting to recovery or perhaps some previous owner flashed a spoofed hboot and you actually do have an unlocked bootloader but don't know it. Did you buy the phone new with this being the first time you've tinkered with it?
Click to expand...
Click to collapse
I went to the States a month ago and I bought it pre-owned in Gamestop, so maybe as you said it is modified. And answering about the TWRP I tried to boot into recovery yesterday but I had no success (I got to the default android recovery).
Summing up I'll just buy the full version of the sunshine app and do this thing in the proper way, thank you for your help and time.
coderch123 said:
I went to the States a month ago and I bought it pre-owned in Gamestop, so maybe as you said it is modified. And answering about the TWRP I tried to boot into recovery yesterday but I had no success (I got to the default android recovery).
Summing up I'll just buy the full version of the sunshine app and do this thing in the proper way, thank you for your help and time.
Click to expand...
Click to collapse
Why not verify first you are truly s-on with a fastboot getvar all
That way we can make sure someone didn't flash a faux hboot.
Sent from my SM-T810 using Tapatalk
dottat said:
Why not verify first you are truly s-on with a fastboot getvar all
That way we can make sure someone didn't flash a faux hboot.
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Sorry for the delay. I checked it with fastboot getvar all and it is stock, there's nothing wrong with it. S-ON and locked bootloader.